www.ReeltoReel.nl Wiki wikidb https://www.reeltoreel.nl/wiki/index.php/Main_Page MediaWiki 1.44.0 first-letter Media Special Talk User User talk www.ReeltoReel.nl Wiki www.ReeltoReel.nl Wiki talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk 0 6 20 2007-08-19T11:53:37Z Pvdm 2 New page: * [[enhancing the GroupWise Client on Linux]] wikitext text/x-wiki * [[enhancing the GroupWise Client on Linux]] 993ba2a1d2ba13b65d44683452f33de0292f71ba 0 7 21 2007-08-19T11:54:35Z Pvdm 2 New page: How to speed-up and improve the GroupWise linux client appearance When you want to improve the GroupWise linux client appearance, make a launcher icon and enter the following command: /o... wikitext text/x-wiki How to speed-up and improve the GroupWise linux client appearance When you want to improve the GroupWise linux client appearance, make a launcher icon and enter the following command: /opt/novell/groupwise/client/bin/groupwise -ui=gtk And now the java-look has been replaced by a (slightly better looking) GTK look! This tip will speed up the GroupWise Linux Client by switching it over to GTK. Give it a shot and see what you think. 1. From the SLED10 console do the following: SU {enter admin password} cd /opt/novell/groupwise/client/bin vi groupwise 2. Modify this: /opt/novell/groupwise/client/bin/groupwise-bin "$@" so that it says this: /opt/novell/groupwise/client/bin/groupwise-bin -ui=gtk "$@" 3. Save changes and exit. GroupWise will now run from the menus in GTK mode. c734fc99e93f2026e271e6e7a189adb2d5ee40d2 0 11 25 2007-08-19T11:58:56Z Pvdm 2 New page: Fixing CUPS login problems on SuSE SUSE: What Password Do I Use At The Web Interface? SuSE defaults to using Digest passwords and "RunAsUser yes", which means you have to use the lppassw... wikitext text/x-wiki Fixing CUPS login problems on SuSE SUSE: What Password Do I Use At The Web Interface? SuSE defaults to using Digest passwords and "RunAsUser yes", which means you have to use the lppasswd command to add accounts and passwords. To add a user named Steve: lppasswd -a Steve Then enter and confirm a password. SUSE does not follow the normal CUPS defaults and the lppasswd information doesn't follow changes to the normal accounts, causing a lot of confusion. Any problems using this set up should be addressed to SUSE. To set SUSE to the standard default settings of CUPS: 1) Goto /etc/cups/cups.conf 2) Change in <Location /admin> the AuthType: AuthType Basic 3) Change RunAsUser to No. 1816c4fafb9a5007f577b4a2312b45711d4b019e 0 12 27 2007-08-19T12:03:29Z Pvdm 2 New page: Speed up Linux installation Tip: Speeding up the install time on SUSE Linux Applies to: * Novell Linux Desktop 9 * Open Enterprise Server * SUSE Linux Professional 9.3 * S... wikitext text/x-wiki Speed up Linux installation Tip: Speeding up the install time on SUSE Linux Applies to: * Novell Linux Desktop 9 * Open Enterprise Server * SUSE Linux Professional 9.3 * SUSE Linux 10 * SUSE Linux Enterprise Server SYNOPSIS: hdparm - get/set hard disk parameters DESCRIPTION: This cool solution will show you how it is possible to speed up the install time of your CD-ROM installation of SUSE Linux by using Linux shell command hdparm. hdparm is an a command line interface to various ATA/IDE hard disk device drivers.1 Warning, 'hdparm' may force your system to use higher values without regards to your hardware's limitations. It is a risk to use this program improperly and may cause damage to your systems. Please use extreme caution and do not exceed your hardwares limitations. Additionally WE TAKE NO RESPONSIBILITY FOR DAMAGED HARDWARE OR CORRUPTED DATA. Know bugs are listed on Source Forge's website see notes for information The following steps are needed to use hdparm in the installation of your SuSE LINUX system. Please note that this command only works with IDE devices, CDROMS and Hard-drives. * Place the SUSE Linux disk 1; the install cd in the CD-ROM and boot to that drive. * On the first screen enter desired parameters you need to perform your specific SuSE LINUX installation. * The next screen is the Licensing Screen; on this screen select the "I Agree" button. * Next is the Language screen; on this screen choose your language and click "Accept". * This is the bit we have been waiting for: This next screen is Installation Setting screen. * Here we will drop into a shell prompt by using Ctrl+Alt+F2. This key combination will normally take you out of your Xwindow session and drop you into a terminal (tty2). Since we are in the process of installing SUSE LINUX, this key combination will take us away from the installation screen and drop you in to a terminal (tty2), or command prompt. Don't worry. Your installation is still there. You can return by using the Alt+F7. * Once on the command line type: hdparm /dev/hda thenENTER You will see something similar to this. /dev/hda: multcount = 16 (on) IO_support = 0 (default 16-bit) unmaskirq = 0 (off) using_dma = 0 (off) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 9726/255/63, sectors = 156250000, start =34523 * Notice the multcount is set to 16, using_dma is set to off, and that the IO Support is set to 16 bit. * Re-type the command: hdparm -c1 -d1 -m1 /dev/hda ENTER Comparing the differences from the last time, you should now see that mulcount is set to 1, or on, IO support is now 32 bit and.using_dma is turned on. /dev/hda: multcount = 1 (on) IO_support = 1 (32-bit) unmaskirq = 0 (off) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 9726/255/63, sectors = 156250000, start = 0 When you complete your desired changes to your devices, you can return to the installation screen by using the Alt+F7. muticount -m is used to get or set the sector count for a device that supports multiple sector IO. IO support -s is used to set the IO setting on a device. Most devices are set to use 16bit. By setting this to 1 it turns on 32bit IO for faster transfers of information. Using_dma -a by default this is turned off. DMA or Direct Memory Access is way to control system memory without using the CPU. If you would like more information about hdparm; browse the official hdparm website at http://sourceforge.net/projects/hdparm/ or additional options may be found in the man pages. You now have the knowledge to decrease your installation times by exerting control over your IDE devices with the hdparm Linux shell command. If you have any questions about this Cool Solution, feel free to drop me an email anytime at tvickers@idltechnology.comDit e-mailadres wordt beschermd tegen spam bots, u heeft Javascript nodig om het te bekijken . ABOUT THE AUTHOR: Tony Vickers is the CTO and founder of IDL technology Group, Inc. IDL has been helping companies implement Enterprise Open Source Technologies since 1994. For more information, please visit us on the web located at www.idltechnology.com Notes 1. Lord, Mark and Leppikangas, Tomi. "hdparm(8)." (Linux man page, 2005), 1. Barr, Joe. "Hdparm and the Zen of data transfer Monday December," Enterprise Linux on the web, 07 October 2005. <http://enterprise.linux.com/article.pl?sid=04/12/14/166253&tid=89> (December 20, 2004). Flickenger, Rob. "Speeding up Linux Using hdparm." Linux Dev Center on the web, 07 October 2005. <http://www.linuxdevcenter.com/pub/a/linux/2000/06/29/hdparm.html> (June 29, 2000). Lord, Mark. "hdparm(8)." <http://sourceforge.net/projects/hdparm/ hdparm> (April, 2005). KNOWN BUGS: 1. ATA security options does not always work, error message: Problem issuing security command: Cannot allocate memory (http://sourceforge.net/tracker/?atid=736682&group_id=136732&func=browse). 2. hdparm -t with 2 disks: WD (hdb) and Seagate(hda). hdparm -t /dev/hda -Timing buffered disk reads: -1504 MB in xxx seconds = MB/sec an infinite value (http://sourceforge.net/tracker/?atid=736682&group_id=136732&func=browse). 1. When making 6.0 or 6.1 an "987: IDE_DRIVE_TASK_OUT undeclared" error occur(http://sourceforge.net/tracker/?atid=736682&group_id=136732&func=browse). 2. Acoustic management for SAMSUNG SP1614N disk the -M option to control the acoustic level, but it seems non-functional (http://sourceforge.net/tracker/?atid=736682&group_id=136732&func=browse). a8dc04a18b883a191ed8190646fda65bc03001e3 0 15 33 2007-08-19T12:09:06Z Pvdm 2 New page: How convert flv2mpg or flv to other formats: http://www.mydigitallife.info/2006/12/14/free-online-flv-converters/ http://www.mplayerhq.hu/design7/dload.html ,example: mencoder input.flv... wikitext text/x-wiki How convert flv2mpg or flv to other formats: http://www.mydigitallife.info/2006/12/14/free-online-flv-converters/ http://www.mplayerhq.hu/design7/dload.html ,example: mencoder input.flv -ofps 15 -vf scale=300:-2 -oac lavc -ovc lavc -lavcopts vcodec=msmpeg4v2:acodec=mp3:abitrate=64 -o output.avi f18b577a267f6ffef37fc72f697fe4056abd8216 0 17 35 2007-08-19T12:11:24Z Pvdm 2 New page: Enable suspend to ram on notebooks with ATI card ATI driver and suspend-to-ram It appears that a lot of people (running openSUSE 10.2) are having issues with the last releases of the pro... wikitext text/x-wiki Enable suspend to ram on notebooks with ATI card ATI driver and suspend-to-ram It appears that a lot of people (running openSUSE 10.2) are having issues with the last releases of the proprietary ATI fglrx Linux driver in combination with suspend to RAM. Especially version 8.33.6 but also 8.32.5 seem to hang up the system in most cases. At Moosy we wanted our beloved suspend function back and started to investigate. We found this document at AMD which simply stated: "ATI Engineering is aware of this issue and is investigating." Not very promising. When digging deeper into this, we found a solution that may work for you. This has been tested on some Dell Latitude and IBM Thinkpad laptops and has been found to work on those. YMMV. '''openSUSE powermanagement''' openSUSE works with s2ram and pm-utils as a framework for suspending. See the s2ram page on the openSUSE site. S2ram does the actual suspending and comes with several options for different machines. Pm-utils runs distro-specific scripts for preparing the system for suspend (unloading modules, etc.) We found that adding some options to s2ram and removing some SUSE scripts from pm-utils resulted in working suspend-to-ram with the latest fglrx drivers. Start: s2ram First see if you can get your machine to suspend using s2ram. To do this, open a terminal and become root. Type s2ram and hope for the best. The command comes with several options and the one that does the trick for ATI cards seems to be -m which saves and sets the VBE mode. We found that on Dell machines, the following combination works: s2ram -f -m while on IBM machines s2ram -f -s -m or even s2ram -f -s -m -a 3 was necessary. Experiment some, but keep the -m option. You may want to check the s2ram suggestions for you machine using s2ram -n and checking the line starting with "Fixes". Add s2ram options to your setup The options that work for you need to be put into the suspend configuration. To do this, open the file /etc/pm/config as root and search for S2RAM_OPTS="". Add the options that you needed to add for your machine here, preceded by a space, like this: S2RAM_OPTS=" -f -m" Remove pm-utils scripts Now the not-so-funny part: we discovered that after this, suspending still did not work! It turned out that some of the scripts that are run by pm-utils cause this. The scripts are located in /etc/pm/hooks and we needed to remove at least the cpufreq and videobios scripts. So, to do this enter cd /etc/pm/hooks and do a rm 80videobios 94cpufreq 99Zgrub (the last one may not be necessary). Please note that removing these scripts may break things (like suspend to disk). After this, reboot to ensure that the changes are picked up by the powermanagement system. If this worked for you, let us know!! We tested on Dell D810, D600 and IBM t43, t60p systems. 1dc5185dab7c8210935f920de0fc4b05f2bb6d73 0 19 40 2007-08-19T12:13:42Z Pvdm 2 [[Prob]] moved to [[Problem w/ ZEN/rug/rpm database]] wikitext text/x-wiki #REDIRECT [[Problem w/ ZEN/rug/rpm database]] 41289e36e6d735d3fb9b4619240060928b469730 0 23 49 2007-09-25T18:09:19Z Root 1 New page: A much eaiser way to verify and repair PAR2 files. This assumes you have par2 installed As a normal user: * Open konquer and select settings-->configure konqueor-->File associations--->... wikitext text/x-wiki A much eaiser way to verify and repair PAR2 files. This assumes you have par2 installed As a normal user: * Open konquer and select settings-->configure konqueor-->File associations--->Add--->par2--->Add *You should add *.par2 and then in all caps *.PAR2 *Click Add under application preference order---->type the word konsole------>command for konsole is konsole --noclose -e par2 r That will enable you to double click par2 files and a konsole window will open and verify and repair if needed. The window will stay open when finished so you can be sure all went well. d38fb04ab585b4fb736e2dc3f06b15c46926ccff 0 25 56 55 2007-10-14T18:43:04Z Root 1 wikitext text/x-wiki == Installing Newsleecher in Wine == As for installing your licence, I recommend exporting the registry key from your Windows install, edit the first line in it where it says 'Windows Registry Editor Version 5.00' and change it to 'REGEDIT4'. Then open a terminal and type 'wine regedit'. In the registry editor, choose file, import and point to the exported registry file. You can also manually enter every key in the registry, copying the data from Windows to Linux. * The key is located in HKLM\Software\05970870 * Search for your Licence ID. Found in Help > About. Be sure to untick 'match whole string' when searching the registry. It's 'swXXXXXXXX'. *Not all licenses start with sw. Some start with DI or NL. 768fc3806d4ada7224ce0c43f493ba2798d01958 0 26 60 58 2007-11-11T10:30:41Z Root 1 [[Installatie openftp in OpenSUSE 10.3]] moved to [[Installatie openftd in OpenSUSE 10.3]] wikitext text/x-wiki ==Installatie OpenFTD in OpenSUSE 10.3== '''De installatie bestaat uit 2 delen: * eerst de installatiebron toevoegen * de daadwerkelijke installatie De installatiebron toevoegen: # open YaST # klik op 'Software' en dan op 'Software repositories' # klik op 'Add' en dan op 'Specify URL' en 'Next' # vul bij 'Repository Name' b.v. 'OpenFTD' in # vul bij 'URL' in: 'http://openftd.org/releases/openSUSE_10.3' # Finish. Om het pakket te installeren: # klik in YaST op 'Software Management' # Tijp in de 'Search'-box 'openftd' en klik op 'Search' # selecteer alle gevonden openFTD pakketten en klik op 'Accept' # accepteer evt. de Automatic changes die nog gevonden worden # de software wordt geïnstalleerd bde45988fe265f2175ba1004a7b05788fdd19313 0 27 61 2007-11-11T10:30:41Z Root 1 [[Installatie openftp in OpenSUSE 10.3]] moved to [[Installatie openftd in OpenSUSE 10.3]] wikitext text/x-wiki #REDIRECT [[Installatie openftd in OpenSUSE 10.3]] ab49c0b67c6815d95e1fa89bd8a3dcdc53788761 0 28 64 63 2007-12-05T12:04:49Z Root 1 wikitext text/x-wiki <!-- SDB information SDB:title: Speeding up Package Manager Stack SDB:author: msmeissn SDB:date: 2007-09-25 --> [[Category:SDB:10.3|C]] [[Category:SDB:Installation|C]] [[Category:SDB:YOU|C]] = Speeding up the package manager = Package Management is one part of the system where massive databases are thrown around, changed incrementally and is generally used heavily. Due to incremental nature of modifications it will cause the databases used to fragment, both internally (in the database blob) and externally (on the disk). In openSUSE 10.3 we have two kinds of databases for package management. * The zypp cache SQLITE database in <code>/var/cache/zypp/zypp.db</code>. * The RPM database in <code>/var/lib/rpm/</code>. == Defragment internally == *Cleaning up sqlite databases can be done using the <code>VACUUM</code> command. :For the ZYPP cache database: :<code>sqlite3 /var/cache/zypp/zypp.db vacuum</code> :Or alternatively regenerate it from scratch: :<code>rm /var/cache/zypp/zypp.db ; zypper refresh</code> *Defragmenting the RPM database :After largish update it is helpful to run <code>rpm --rebuilddb</code> once. :This is just necessary after lots of packages changed/updated/installed and takes some time (10 minutes on a Laptop). == Defragment externally == While Linux filesystems try to not create heavily fragmented files, the slow increasing nature of the databases used in packagemanagement has fragmentation patterns. So to best way to get rid of it, is to recreate the files using the pattern: <pre> cp file file.new # check for errors! rm file mv file.new file </pre> *zypp database :Either remove it and regenerate it using <code>zypper refresh</code> or just apply :the cp/rm/mv on <code>/var/cache/zypp/zypp.db</code>. *RPM database :Use the cp/rm/mv trick on <code>/var/lib/rpm/Packages, Basenames, Filemd5s, Dirnames</code> == Sample script == <pre> #!/bin/sh sqlite3 /var/cache/zypp/zypp.db vacuum rpm --rebuilddb # takes long for fn in /var/cache/zypp/zypp.db \ /var/lib/rpm/Packages \ /var/lib/rpm/Filemd5s \ /var/lib/rpm/Dirnames \ /var/lib/rpm/Basenames do cp $fn $fn.new || exit 1 rm $fn mv $fn.new $fn done </pre> <keyword>zypp,rpm,speed,package management</keyword> 64b454132018eaf029e96cd9f778d790cea2c547 0 29 67 66 2007-12-09T21:32:04Z Root 1 wikitext text/x-wiki Aan elke harddisk in een Linux systeem kun je een aparte time-out geven wanneer deze een spin-down moet gaan doen (standby / sleepmode). Zodra een harddisk in standmode staat gebruikt deze fors minder stroom. Hiervoor kun je het volgende commando gebruiken hdparm -S 60 /dev/sdd Met bovenstaande commando wordt er een time-out toegekend van 5 minuten aan de systeem disk. Zodra de systeem disk langer dan 5 minuten niet gebruikt wordt dan zal deze een spin-down gaan doen. 1 Minuut is 12 'eenheden' van 5 seconden. bron: http://www.olino.org/articles/2007/02/25/het-bouwen-van-een-zuinige-server-deel-3 fa54038b16d0c20e4917fc87e51da6d784770432 0 18 68 39 2007-12-12T07:47:08Z Root 1 wikitext text/x-wiki '''Problem w/ ZEN/rug/rpm database ''this problem is obsolete, it happened with OpenSUSE 10.2 and is no longer an issue in 10.3'' Things to try when your openSUSE gets errors with the package database: rm -rf /var/tmp/* && rczmd restart && rug refresh works around the problem. I'm not sure how to reproduce it though. It seems to happen randomly. a6ca8a4d9a8b8e2902b59551c13652506006a4ea 0 31 71 70 2007-12-13T15:20:11Z Root 1 wikitext text/x-wiki In order for your clients to automatically recognize the printers that CUPS has, add/edit the following setting in /etc/cups/cupsd.conf: BrowseAddress @LOCAL In this way, your clients won't have to do anything, as their (local) CUPS server will recognize the broadcasts from your (global) CUPS server! a8cad14e6a29bd80296ee3507ba1a5e2153de7c6 0 32 73 2007-12-14T10:29:42Z Root 1 New page: ==In KDE:== Regional settings keyboard layout xkb options | enable compose key position | menu is compose wikitext text/x-wiki ==In KDE:== Regional settings keyboard layout xkb options | enable compose key position | menu is compose 92c1372949663c764eddc0172f60fb7b145ccc6d 0 34 86 2008-02-03T19:14:44Z Root 1 New page: To make an ISO from your CD/DVD, place the media in your drive but do not mount it. If it automounts, unmount it. for DVD: dd if=/dev/dvd of=dvd.iso for CD: dd if=/dev/cdrom of=cd.i... wikitext text/x-wiki To make an ISO from your CD/DVD, place the media in your drive but do not mount it. If it automounts, unmount it. for DVD: dd if=/dev/dvd of=dvd.iso for CD: dd if=/dev/cdrom of=cd.iso SATA device dd if=/dev/sr0 of=file.iso SCSI device: dd if=/dev/scd0 of=cd.iso a662cce713cddb31bd441348509f4536cff8d6c0 0 4 89 88 2008-02-25T19:54:15Z Root 1 wikitext text/x-wiki How to make Audacity work with ALSA If you want to work with the audio editing software Audacity, and you get an error starting Audacity, you can try the following: start audacity with the following command: >aoss audacity This will start audacity with the alsa osscompatibility layer. or try selecting in Preferences ALSA Default as the sound device ==How to make MP3 support working== sudo ln -s /usr/lib/libmp3lame.so.0 /usr/lib/libmp3lame.so 3318fa2ff694c8ad7a22220c5e3dba0ce45c79f6 0 35 91 2008-02-26T15:38:37Z Root 1 New page: *use iostat (package sysstat) *siga (outputs in HTML) *sitar (SLES) wikitext text/x-wiki *use iostat (package sysstat) *siga (outputs in HTML) *sitar (SLES) 4de30a3dd997ca3f8c19aa2ca2148c5db05c469f 0 37 95 2008-03-16T19:52:56Z Root 1 New page: hal cdrom polling hal is a core component of the various desktop environments and deals with all sorts of hardware interaction. One component of the hal daemon is the part where it polls t... wikitext text/x-wiki hal cdrom polling hal is a core component of the various desktop environments and deals with all sorts of hardware interaction. One component of the hal daemon is the part where it polls the cdrom drive regularly (as often as once every two seconds!) to see if the user has inserted a CD. This is used, for example, to automatically open a new window with a file browser for the CD. Such regular polling will keep the hardware awake somewhat; the amount of power consumed depends on the exact type of CDROM drive. It also depends on the presence of the ALPM feature. If you rarely or never insert CDs (for example because the machine in question is a server located 3000 miles away), you can save some power by stopping this polling. Current versions of hal have a special command for this: hal-disable-polling --device /dev/scd0 Note that this means that you will not get a pop-up window if you insert a CD. To enable this polling again, use the this command: hal-disable-polling --device /dev/scd0 --enable-polling Newer SATA-based CDROM drives have the capability to notify the machine when a CD gets inserted, making polling unnecessary. Both the kernel and hal are currently undergoing development to detect and support this capability, so that polling is not needed at any time for these devices. 363ec8b8284097fc81a5820edfd424eb6459e0b6 0 40 102 2008-04-24T20:26:11Z Root 1 New page: ==Migratie Joomla vaan 1.5== # d/l migratie component # maak nieuwe site aan naast de oude # admin -> installer -> components (install php-zlib) # installeer extra plugins? # start migrat... wikitext text/x-wiki ==Migratie Joomla vaan 1.5== # d/l migratie component # maak nieuwe site aan naast de oude # admin -> installer -> components (install php-zlib) # installeer extra plugins? # start migratie # installeer nieuwe joomla ## stap 6, kies voor load migration script, old table prefix "jos_" # verwijder installatiemap fd221c39774cfe6d799fc931f8e6984f0157bb77 0 41 107 106 2008-04-28T18:20:31Z Root 1 wikitext text/x-wiki ==Install all updates using Zypper== The following command gives you ALL updates: zypper up -t package 0f4c7cbc2b477557dddd573c93f23858d9617642 0 5 110 109 2008-04-28T18:22:44Z Root 1 wikitext text/x-wiki '''How to make a portion of an image transparent using The Gimp''' Sometimes you want to make a certain portion of an image transparent. This is for instance to make an image look good, placed on a background on a web page. Remember that only .GIF and .PNG support this feature, NOT .JPG!! This can easily be done using The Gimp. 1. Open your image in the Gimp. File -> Open. 2. Right click the image and go to LAYERS then ADD ALPHA CHANNEL. This is the transparency layer. 3. Right click on the image again and go to SELECT and then BY COLOR. 4. Now click on the color in the image you want to be transparent. These colors will now show up outlined. 5. Right click on the image again and go to EDIT and then down to CLEAR. This should now erase the outlined color you just picked from the image and the "transparent gimp checkerbox" should show through. This is the Gimps way of showing you that section is now transparent. 6. Right click on the image and choose SAVE AS and make sure to save as a GIF file if you want the transparency to work on the web. Select CONVERT TO INDEXED if necessary. It is also possible to SAVE AS... PNG 7. That's it! 0b094e2a2d880afc282c2631b68d9a30faee8073 0 44 124 123 2008-07-17T19:51:25Z Root 1 wikitext text/x-wiki Or commandline friendly su -c “OCICLI http://opensuse-community.org/ati.ymp” su -c “OCICLI http://opensuse-community.org/nvidia.ymp” One more commandline way via zypper: NVIDIA: zypper sa http://download.nvidia.com/opensuse/11.0 nvidia zypper in x11-video-nvidiaG01 ATI: zypper sa http://www2.ati.com/suse/11.0 ati zypper in x11-video-fglrxG01 ===Other codecs etc=== Open terminal to run these commands or click on the link in web browser: Compiz Fusion with almost everything: su -c “OCICLI http://download.opensuse.org/repositories/X11:/XGL/openSUSE_11.0/compiz-fusion-all.ymp” Codecs pack for Gnome: su -c “OCICLI http://opensuse-community.org/codecs-gnome.ymp” Codecs pack for KDE: su -c “OCICLI http://opensuse-community.org/codecs-kde.ymp” When NVIDIA and ATI drivers are available, they can be installed in a same way too. Note: Quotes are necessary, make sure there is no “wordpress effect” when you copy paste the above commands in shell f5697a9a72cc754e9f77c40332a2a15a96581614 0 45 133 132 2008-08-13T06:57:50Z Root 1 wikitext text/x-wiki ==Method 1 (tested!)== On the bron/zender/source: #dd if=/dev/sda | gzip -c | netcat -l -q 0 -p 2222 On the ontvanger/doel/target: #netcat <ip van server> 2222 | gzip -cd | dd of=/dev/sda This way we get a throughput of 14,1 MB/s, 160 GB in 11543 seconds (3,2 hour) ==Methode 2 (niet getest!)== How do I use netcat to copy hard disk image? Our sample setup HostA // 192.168.1.1 sda NETWORK sdb HostB // 192.168.1.2 Your task is copy HostA /dev/sda to HostB's /dev/sdb using netcat command. First login as root user Command to type on hostB (receiving end ~ write image mode) You need to open port on hostB using netcat, enter : # netcat -p 2222 -l |bzip2 -d | dd of=/dev/sdb Where, * -p 2222 : Specifies the source port nc should use, subject to privilege restrictions and availability. Make sure port 2222 is not used by another process. * -l : Used to specify that nc should listen for an incoming connection rather than initiate a connection to a remote host. * bzip2 -d : Compresses image using the Burrows-Wheeler block sorting text compression algorithm, and Huffman coding. This will speed up network transfer ( -d : force decompression mode) * dd of=/dev/sda : /dev/sda is your hard disk. You can also specify partition such as /dev/sda1 Command to type on hostA (send data over a network ~ read image mode) Now all you have to do is start copying image. Again login as root and enter: # bzip2 -c /dev/sda | netcat hostA 2222 OR use IP address: # bzip2 -c /dev/sda | netcat 192.168.1.1 2222 This process takes its own time. A note about latest netcat version 1.84-10 and above If you are using latest nc / netcat version above syntax will generate an error. It is an error to use -l option in conjunction with the -p, -s, or -z options. Additionally, any timeouts specified with the -w option are ignored. So use nc command as follows. On hostA, enter: # nc -l 2222 > /dev/sdb On hostB, enter: # nc hostA 2222< /dev/sda OR # nc 192.168.1.1 2222< /dev/sda Using a second machine (hostB), connect to the listening nc process at 2222 (hostA), feeding it the file (/dev/sda)which is to be transferred. You can use bzip2 as follows. On hostA, enter: # nc -l 2222 | bzip2 -d > /dev/sdb On hostB, enter: # bzip2 -c /dev/sda | nc 192.168.1.1 2222 596dd784ccfbb06af280a0170fecaeaf802e8f70 0 48 143 2008-09-23T13:10:00Z Root 1 New page: nmap -sV -P0 -O [server] wikitext text/x-wiki nmap -sV -P0 -O [server] 1e258c22f009568df29c0bfe407a41b04c025d4a 0 50 150 2008-11-02T21:18:43Z Root 1 New page: ==How to locally cache zypper update files== Maybe someday you try zypper dup to actualize your distribution and in middle of process it fail, because you are disconnected or some package... wikitext text/x-wiki ==How to locally cache zypper update files== Maybe someday you try zypper dup to actualize your distribution and in middle of process it fail, because you are disconnected or some packages is actualized before you download it (especially on factory this can happen). It is more safety download packages at first and then install from this local files. How todo this is little tricky, at first you must enable caching downloaded files (I do it only for remote connection): zypper mr –keep-packages –remote So now you cache all downloaded files and now try testing run of dup. Trick is that all packages download for that test is cached. zypper dup –dry-run Now if you have slow connection I reccomend also disable autorefresh for all repositories, because if repository is refreshed before dup, you can easily find that some packages is newer than package in cache and you must download it. zypper mr –all –no-refresh Now is everything prepared for zypper dup, which use files from cache. Cache can take quite lot of disk space, so after dup you can clean it. zypper clean And thats all. This features work from OpenSuse 11 and you can also use this trick for zypper update or zypper install. ae78cdf6c4a5489163cdc5d6282fbd92200622dc 0 51 154 153 2008-11-10T16:44:04Z Root 1 wikitext text/x-wiki ==Adding partitions== When new disks are added, existing raid partitions can be grown to use the new disks. After the new disk was partitioned, the RAID level 1/4/5/6 array can be grown for example using this command (assuming that before growing it contains three drives): mdadm --add /dev/md1 /dev/sdb3 mdadm --grow --raid-devices=4 /dev/md1 The process can take even 10 hours. There is a critical section at start, which cannot be backed up. To allow recovery after unexpected power failure, an additional option <code>--backup-file=</code> can be specified. ==Expanding existing partitions== It is possible to migrate the whole array to larger drives (e.g. 250 GB to 1 TB) by replacing one by one. In the end the number of devices will be the same, the data will remain intact, and you will have more space available to you. ===Extending an existing RAID array=== In order to increase the usable size of the array, you must increase the size of all disks in that array. Depending on the size of your disks, this may take days to complete. It is also important to note that while the array undergoes the resync process, it is vulnerable to irrecoverable failure if another drive were to fail. It would (of course) be a wise idea to completely back up your data before continuing. First, choose a drive and completely remove it from the array mdadm -f /dev/md0 /dev/sdd1 mdadm -r /dev/md0 /dev/sdd1 Next, partition the new drive so that you are using the amount of space you will eventually use on all new disks. For example, if you are going from 100 GB drives to 250 GB drives, you will want to partition the new 250 GB drive to use 250 GB, not 100 GB. Also, remember to set the partition type to '''0xDA''' - Non-fs data (or '''0xFD''', Linux raid autodetect if you are still using the deprecated autodetect). fdisk /dev/sde Now add the new disk to the array: mdadm --add /dev/md0 /dev/sde1 Allow the resync to fully complete before continuing. You will now have to repeat the above steps for *each* disk in your array. Once all of the drives in your array have been replaced with larger drives, we can grow the space on the array by issuing: mdadm --grow /dev/md0 --size=max The array now represents one disk using all of the new available space. ===Extending the filesystem=== Now that you have expanded the underlying partition, you must now resize your filesystem to take advantage of it. For an ext2/ext3 filesystem: resize2fs /dev/md0 For a reiserfs filesystem: resize_reiserfs /dev/md0 Please see filesystem documentation for other filesystems. ===LVM: Growing the PV=== LVM (logical volume manager) abstracts a logical volume (that a filesystem sits on) from the physical disk. If you are used to LVM then you are likely used to growing LVs (logical volumes), but what we grow here is the PV (physical volume) that sits on the ''md'' device (RAID array). For further LVM documentation, please see the [http://tldp.org/HOWTO/LVM-HOWTO/ Linux LVM HOWTO] Growing the physical volume is trivial: pvresize /dev/md0 A before-and-after example is: root@barcelona:~# pvdisplay --- Physical volume --- PV Name /dev/md0 VG Name server1_vg PV Size 931.01 GB / not usable 558.43 GB Allocatable yes PE Size (KByte) 4096 Total PE 95379 Free PE 42849 Allocated PE 52530 PV UUID BV0mGK-FRtQ-KTLv-aW3I-TllW-Pkiz-3yVPd1 root@barcelona:~# pvresize /dev/md0 Physical volume "/dev/md0" changed 1 physical volume(s) resized / 0 physical volume(s) not resized root@barcelona:~# pvdisplay --- Physical volume --- PV Name /dev/md0 VG Name server1_vg PV Size 931.01 GB / not usable 1.19 MB Allocatable yes PE Size (KByte) 4096 Total PE 238337 Free PE 185807 Allocated PE 52530 PV UUID BV0mGK-FRtQ-KTLv-aW3I-TllW-Pkiz-3yVPd1 The above is the PV part after md0 was grown from ~400GB to ~930GB (a 400GB disk to a 1TB disk). Note the ''PV Size'' descriptions before and after. Once the PV has been grown (and hence the size of the VG, volume group, will have increased), you can increase the size of an LV (logical volume), and then finally the filesystem, eg: lvextend -L +50G -n home_lv server1_vg resize2fs /dev/server1_vg/home_lv The above grows the ''home_lv'' logical volume in the ''server1_vg'' volume group by 50GB. It then grows the ext2/ext3 filesystem on that LV to the full size of the LV, as per ''Extending the filesystem'' above. 12c41f91b2cd5b550828ba345c1d69425ecc87af 0 53 173 2008-11-17T20:38:40Z Root 1 New page: # Install guest additions in windows guest # launch the software # make sure the window is neither fully maximized nor minimised # choose Machine, Seamless Mode To exit VitrualBox, you w... wikitext text/x-wiki # Install guest additions in windows guest # launch the software # make sure the window is neither fully maximized nor minimised # choose Machine, Seamless Mode To exit VitrualBox, you will need to exit seamless mode first: # press Hostkey - L c0d9b5375d42ea76c3d2fe0fc0896115c26c7918 0 55 182 181 2008-12-07T13:17:36Z Root 1 wikitext text/x-wiki sshfs user@host: /mnt/ Once that’s done, the remote filesystem is mounted as the directory “rsync” and I can copy and move files just like they’re local. 46ccb2e3dd0ce1517ed1e943fb234411137ed593 0 56 186 185 2008-12-08T20:07:51Z Root 1 wikitext text/x-wiki 1. Check if there are missing dependencies Code: # LC_ALL=C zypper ve Reading installed packages... Dependencies of all installed packages are satisfied. 2. Check if there are packages installed from the VideoLAN repository Code: $ rpm -qa --queryformat '%{NAME} -> %{VENDOR}\n' | grep -i VideoLAN libdvdcss -> VideoLAN Project (http://www.videolan.org) Only libdvdcss should be installed from the VideoLAN repository. 3. Check your basic multimedia packages Code: $ rpm --verify --query --all 'libav*' 'libpostproc*' 'libswscale*' If it return anything there is a problem, check man rpm for details. No need to reinstall to be sure, this check is 100% sure. 4. Verify you have xine installed and installed from Packman Code: $ rpm --query --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} -> %{VENDOR}\n' libxine1 libxine1-codecs libxine1-1.1.15-44.pm.0-x86_64 -> packman.links2linux.de libxine1-codecs-1.1.15-44.pm.0-x86_64 -> packman.links2linux.de 5. Check your xine packages Code: $ rpm --verify --query --all '*xine*' 6. Verify you have all the gstreamer plugins (codecs) installed and installed from Packman Code: $ rpm --query --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} -> %{VENDOR}\n' gstreamer-0_10-ffmpeg gstreamer-0_10-fluendo-mp3 gstreamer-0_10-fluendo-mpegdemux gstreamer-0_10-fluendo-mpegmux gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-base gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-extra gstreamer-0_10-plugins-ugly gstreamer-0_10-ffmpeg-0.10.5-42.pm.1-x86_64 -> packman.links2linux.de gstreamer-0_10-fluendo-mp3-0.10.7-42.pm.2-x86_64 -> packman.links2linux.de gstreamer-0_10-fluendo-mpegdemux-0.10.15-42.pm.1-x86_64 -> http://packman.links2linux.de gstreamer-0_10-fluendo-mpegmux-0.10.4-42.pm.1-x86_64 -> packman.links2linux.de gstreamer-0_10-plugins-bad-0.10.8-42.pm.1-x86_64 -> packman.links2linux.de gstreamer-0_10-plugins-base-0.10.21-42.pm.1-x86_64 -> packman.links2linux.de gstreamer-0_10-plugins-good-0.10.10-42.pm.3-x86_64 -> packman.links2linux.de gstreamer-0_10-plugins-good-extra-0.10.10-42.pm.3-x86_64 -> packman.links2linux.de gstreamer-0_10-plugins-ugly-0.10.10-42.pm.1-x86_64 -> packman.links2linux.de 7. Check your gstreamer packages Code: $ rpm --verify --query --all '*gst*' 8. Check your MPlayer package Code: $ rpm --verify MPlayer 9. Check your VLC packages Code: $ rpm --verify --query --all '*vlc*' .....UG. /usr/bin/qvlc .....UG. /usr/bin/svlc .....UG. /usr/lib64/vlc/gui/libqt4_plugin.so Like you see in this case there is a problem, but it's just a permissions problem. Anyway it's a packaging problem I'm going to report to Packman so they can fix it. 10. Check your w32codec package Code: $ rpm --verify w32codec-all package w32codec-all is not installed Note that this package only adds support for some rare formats, and only works on 32bits systems. On a x86-64 system it will not make any difference. If after checking all this you are unable to fix your problem open a thread in this forum. But copy & paste (yes, c&p no just "everything seems ok") the commands from this post and your results, so we know you followed them correctly. And also give us a copy of your installed packages... don't say "I have xine from Packman", prove it!!! Code: $ rpm --query --all 'libav*' 'libpostproc*' 'libswscale*' '*xine*' '*gst*' MPlayer '*vlc*' | grep -v avahi | sort amarok-xine-1.4.10-100.pm.1 gstreamer-0_10-0.10.21-42.pm.3 gstreamer-0_10-ffmpeg-0.10.5-42.pm.1 gstreamer-0_10-fluendo-mp3-0.10.7-42.pm.2 gstreamer-0_10-fluendo-mpegdemux-0.10.15-42.pm.1 gstreamer-0_10-fluendo-mpegmux-0.10.4-42.pm.1 gstreamer-0_10-lang-0.10.21-42.pm.3 gstreamer-0_10-plugins-bad-0.10.8-42.pm.1 gstreamer-0_10-plugins-bad-lang-0.10.8-42.pm.1 gstreamer-0_10-plugins-base-0.10.21-42.pm.1 gstreamer-0_10-plugins-base-lang-0.10.21-42.pm.1 gstreamer-0_10-plugins-farsight-0.12.9-0.pm.3 gstreamer-0_10-plugins-good-0.10.10-42.pm.3 gstreamer-0_10-plugins-good-extra-0.10.10-42.pm.3 gstreamer-0_10-plugins-ugly-0.10.10-42.pm.1 gstreamer-0_10-plugins-ugly-lang-0.10.10-42.pm.1 gstreamer-0_10-utils-0.10.21-42.pm.3 gstreamer-utils-0.10.21-42.pm.3 kdemultimedia3-video-xine-3.5.10-5.21 libavc1394-0-0.5.3-104.1 libavcodec52-0.4.9.15866svn-20081117.pm.2304 libavdevice52-0.4.9.15866svn-20081117.pm.2304 libavformat52-0.4.9.15866svn-20081117.pm.2304 libavogadro0-0.8.1-18.1 libavutil49-0.4.9.15866svn-20081117.pm.2304 libgstapp-0_10-0-0.10.8-42.pm.1 libgstinterfaces-0_10-0-0.10.21-42.pm.1 libgstreamer-0_10-0-0.10.21-42.pm.3 libpostproc51-0.4.9.15866svn-20081117.pm.2304 libswscale0-0.4.9.15866svn-20081117.pm.2304 libvlc2-0.9.6-0.pm.1 libvlccore0-0.9.6-0.pm.1 libxine1-1.1.15-44.pm.0 libxine1-aa-1.1.15-44.pm.0 libxine1-codecs-1.1.15-44.pm.0 MPlayer-1.0rc2_r27637-3.pm.3 phonon-backend-gstreamer-0_10-4.2.0-53.3 phonon-backend-xine-4.1.3-59.11 vlc-0.9.6-0.pm.1 vlc-noX-0.9.6-0.pm.1 vlc-qt-0.9.6-0.pm.1 xinetd-2.3.14-115.1 xine-ui-0.99.5-161.1 And to avoid problems... the most important thing I can say you: even if YaST/zypper/updater gives you such an option... **NEVER** ignore a dependency. Change vendor is ok, ignore dependencies never is a good idea. 5efd57fe3960e270f29eda4777f85c70a140c77b 0 42 205 118 2008-12-16T10:34:22Z Root 1 wikitext text/x-wiki ===buslijn 167 castricum centraal -> anna reijnvaansingel === x:19 && x:49 ===tramlijn 14 slotermeer=== x:x4; na 18:00 elk kwartier 346975e65588c5239d6a547dbe86c80979ecf773 0 61 212 211 2008-12-22T19:48:42Z Root 1 wikitext text/x-wiki Let's say you have 2 computers: cpu1: 10.0.0.1 cpu2: 10.0.0.2 Let's say cpu1's screen is left to cpu2's screen. Let's say you want to control cpu1 from cpu2. <s>Let's assume both computers have the same username.</s> # install x2x on cpu1 # enter on cpu2 ssh -X user@cpu1 'x2x -west -to :0' and leave terminal open. And that's it! 8b8adb3b3c6c1285adb1a7eada9b499ba06c763e 0 57 218 217 2009-01-01T18:04:34Z Root 1 wikitext text/x-wiki <s>the mummy: tomb of the dragon emperor die hard 1-4 16 blocks hancock the happening evan almighty the bourne identity the bourne supremacy the bourne ultimatum sex and the city the movie</s> 10,000 bc alien vs predator 1 <s>2</s> pirates o/t carribean curse of the black pearl c9fbc4d33fda8581432b79259ade87d495716d46 0 62 225 224 2009-05-14T07:08:45Z 193.67.0.153 0 wikitext text/x-wiki install=http://provisioning/.......... --> where to boot OS from autoyast=http://provisioning/......... --> where to get autoyast file from 04ae7e83945cb7fe30bbcccd65c7954e25cd4094 0 79 816 342 2011-01-08T16:00:57Z Root 1 wikitext text/x-wiki Suspend to disk works out of the box, but for suspend to ram you need to modify /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux: change: #We only support pm-utils if [ -x "/usr/sbin/pm-suspend" ] ; then export NUM_SECONDS_TO_SLEEP=$seconds_to_sleep /usr/sbin/pm-suspend $QUIRKS RET=$? else # TODO: add support unsupported fi to: # We only support pm-utils #if [ -x "/usr/sbin/pm-suspend" ] ; then # export NUM_SECONDS_TO_SLEEP=$seconds_to_sleep # /usr/sbin/pm-suspend $QUIRKS # RET=$? #else # # TODO: add support # unsupported #fi /usr/sbin/s2ram -f -p -s * Or upgrade to openSUSE 11.3, for in this version the suspend and hybernate works flawlessly. Also the video (with radeon driver) is perfect. f46d9e39c28c8b78c974da8acb1b9f8d7c832085 0 13 1182 30 2011-03-09T14:52:03Z Root 1 wikitext text/x-wiki Reinstall GRUB after Windows install Here is how to reinstall GRUB after you have had to install windows, and windows has overwritten your master boot record (MBR) so that you can't get back into Linux. * boot from install CD (knoppix did not work in my case, use openSUSE CD) sux - <-this is optional, just use 'su' grub find /boot/grub/stage1 // Will print something like (hd0,1) or find /boot/grub/menu.lst root (hd0,1) setup (hd0) <- ignore prompt for partition quit d8459152391077cc0c486b4b27ad55970babfed1 0 98 1183 1181 2011-03-09T14:53:45Z Root 1 wikitext text/x-wiki sheba <pre> sheba:/home/sietske # fdisk -l Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x252c4de0 Device Boot Start End Blocks Id System /dev/sda1 1 192 1536000 27 Unknown Partition 1 does not end on cylinder boundary. /dev/sda2 192 9880 77824000 7 HPFS/NTFS windows C: /dev/sda3 9881 10142 2104515 82 Linux swap / Solaris swap /dev/sda4 * 10143 19457 74822737+ f W95 Ext'd (LBA) /dev/sda5 10143 12753 20972826 83 Linux opensuse 11.2 20G ext4 /dev/sda6 12754 14059 10490413+ 83 Linux /home (11.2) 10G ext4 /dev/sda7 14060 19457 43359403+ 83 Linux opensuse 11.4 41G ext3 <- deze partitie bevat de menu.lst </pre> 5328166ab30520349b9254b29d080fb4c28b0266 0 345 1185 2011-03-12T10:14:11Z Root 1 Created page with " zypper ar -f http://download.opensuse.org/repositories/home:/muzlocker/openSUSE_11.4/ smoothfonts zypper dup -r smoothfonts" wikitext text/x-wiki zypper ar -f http://download.opensuse.org/repositories/home:/muzlocker/openSUSE_11.4/ smoothfonts zypper dup -r smoothfonts ed7d51226aad2cb8095720ad91c43fd5396a413d 0 346 1187 2011-03-25T13:02:52Z Root 1 Created page with "This guide is a summary of the steps I take to customize a default installation of openSUSE. This particular guide was rewritten for openSUSE 11.2, but most stuff should be app..." wikitext text/x-wiki This guide is a summary of the steps I take to customize a default installation of openSUSE. This particular guide was rewritten for openSUSE 11.2, but most stuff should be applicable to other versions as well. ==first: repos== first, type # zypper lr -d # | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service -+--------------+-----------------------+---------+---------+----------+------+-----------------------------------------------------------------+-------- 1 | repo-debug | openSUSE-11.3-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/11.3/repo/oss/ | 2 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | Yes | 99 | NONE | http://download.opensuse.org/distribution/11.3/repo/non-oss/ | 3 | repo-oss | openSUSE-11.3-Oss | Yes | Yes | 99 | NONE | http://download.opensuse.org/distribution/11.3/repo/oss/ | 4 | repo-source | openSUSE-11.3-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/11.3/repo/oss/ | 5 | repo-update | openSUSE-11.3-Update | Yes | Yes | 99 | NONE | http://download.opensuse.org/update/11.3/ | *delete '''source''' and '''debug''' repos and '''installation dvd''' repo zypper rr < number of repo | name of repo | alias of repo> *add community repos: Packman, VLC etc. zypper ar -f http://download.videolan.org/pub/videolan/vlc/SuSE/11.2/ vlc zypper ar -f http://ftp.skynet.be/pub/packman/suse/11.2/ packman *add KDE 4.3 repos (for updates KDE) zypper ar -f http://download.opensuse.org/repositories/KDE:/43/openSUSE_11.2/ kde43 zypper ar -f http://download.opensuse.org/repositories/KDE:/KDE4:/Community/openSUSE_11.2_KDE_43/ kde43community *or better still, the updated KDE4.4 repos: zypper ar -f http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.2/ kde44 zypper ar -f http://download.opensuse.org/repositories/KDE:/KDE4:/Community/openSUSE_11.2/ kde44comm zypper ar -f http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.2/ kde44play In the end you should have the following repos: #oss #non-oss #update #kde43 or kde44 #kde43community or kde44comm #packman #vlc #nvidia/ATI ==Kernel stuff== Install this stuff now, because sooner or later you will need them. And sometimes the install/compile of a kernel module will fail without these zypper in -y kernel-source linux-kernel-headers kernel-syms make gcc ==utils== zypper in -y mc findutils-locate nmap ==For multimedia stuff:== # zypper in -y flash-player mplayer ffmpeg a52dec mencoder x264 faac w32codec-all vlc optional: # zypper in -y gstreamer-0_10-plugins-good xine-browser-plugin swfdec-browser-plugin gxine-browser-plugin gstreamer-0_10-plugins-bad mplayerplug-in libxine1-codecs ==Language:== zypper in -y ispell-dutch myspell-dutch If you have installed from liveCD, localization may be missing: zypper in -y kde4-l10n-nl kde4-l10n-nl-data kde4-l10n-nl-doc ==firefox:== *install add-ons: adblock, xmarks *add 'new tab' button in buttonbar *configuration: **download location always ask, close when ready etc **start with blank page **do not remember history, suggest from bookmarks **search for text when I start typing **no check my spelling as I type **no check to see if FF is default browser *install silverlight plugin http://go-mono.com/moonlight-beta/ *type about:config in addressbar and change: **network.dns.disableIPv6 -> true **create this one: content.notify.backoffcount -> 5 **also create nglayout.initialpaint.delay -> 0 **network.http.pipelining true **network.http.proxy.pipelining true **network.http.pipelining.maxrequests 8 ==KDE:== *edit /etc/sysconfig/windowmanager and change this option to 'no' KDE_USE_IPV6="no" *taskbar: **add system monitor CPU usage widget **digital clock: add day of week *add yast2 and configure desktop to quick start area (next to suse-icon) *configure desktop - personal settings: **region and language: region: dutch. add dutch to languages **advanced -> session manager: start KDE with empty session **autostart: yakuake **desktop screensaver: random *desktop: add analogue clock widget *for extra KWIN themes: # zypper in kde4-windeco-aurorae kde4-windeco-chromi kde4-windeco-crystal kde4-windeco-dekorator kde4-windeco-nitrogen : and go to System Settings / Appearance / Windows / choose for example the '''aurorae''' theme engine with the '''example''' theme ==Yast2:== *configure NTP settings 194.109.22.18 (XS4All time server) or choose from pool.ntp.org ==OOo== *User details *quickstarter ==Printer configuration== *cups printer 192.168.1.1 ++ALWAYS USE IP++ ==Power settings== ==network mounts== cb43ca60db1a22291829d1c408df8f0fafdb9b39 0 33 1188 278 2011-05-11T12:02:32Z Root 1 wikitext text/x-wiki This document shows quick and dirty how to install a working PXE boot server on openSUSE We start of course with a working server with a static IP address and a working DHCP server somewhere (could be on your server or on your home router or something else). If you haven't got one already, please make sure that you get this working before you continue! * install the atftp and syslinux package s #zypper in atftp syslinux * possibly create the /tftpboot/pxelinux.cfg dir #mkdir /tftpboot/pxelinux.cfg * possibly open port in FireWall * copy the file /usr/share/syslinux/pxelinux.0 to /tftpboot #cp /usr/share/syslinux/pxelinux.0 /tftpboot * create the file /tftpboot/pxelinux.cfg/default (#vi /tftpboot/pxelinux.cfg/default) with the following content: default linux prompt 1 timeout 30 label linux kernel linux append initrd=initrd splash=silent showopts * or put file 'message' in /tftpboot with the following example content: Welcome to Provisioning! Choose one of the following options and press <return>. sles10.2 - SUSE Linux Enterprise Server SP2 32 bit sles10.2_64 - SUSE Linux Enterprise Server SP2 64 bit opensuse11_32 - OpenSUSE 11, 32 bit opensuse11_64 - OpenSUSE 11, 64 bit hardy - Ubuntu 8.04 (Hardy Heron) thin - Boot thin client next - Boot from next BIOS device (default) disk - Boot from first BIOS disk * put 2 files '''initrd''' and '''linux''' in the /tftpboot dir :32 bit: from the /boot/i386/loader directory on the CD/DVD :64 bit: from the /boot/x86_64/loader directory on the CD/DVD That should do the trick! 5f9d86a8019a08cb3e34a48bc3bbdeba46b60f33 0 348 1206 2011-07-01T12:37:58Z Root 1 Created page with "omliggende dorpen met hotels: hoenderloo otterloo overig: http://maps.google.nl/maps/place?cid=17041564054345962223&q=hotel&checkin_date=&num_nights=0&ved=0COkBEPoLMAc&sa=X&..." wikitext text/x-wiki omliggende dorpen met hotels: hoenderloo otterloo overig: http://maps.google.nl/maps/place?cid=17041564054345962223&q=hotel&checkin_date=&num_nights=0&ved=0COkBEPoLMAc&sa=X&ei=sL0NTqXnJsv8Od7Gtf4O&sig2=TJLlU4yZNIzXahhUPjNsqA http://www.grootwarnsborn.nl/ 2fda72662afda09cedd76e91845cb7239695f288 0 349 1210 2011-07-06T06:56:39Z Root 1 Created page with "<pre> lap088:/home/pvdm # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sun Jul 3 19:04:10 CEST 2011 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootl..." wikitext text/x-wiki <pre> lap088:/home/pvdm # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sun Jul 3 19:04:10 CEST 2011 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader default 1 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,1)/boot/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 11.4 - 2.6.37.6-0.5 root (hd0,1) kernel /boot/vmlinuz-2.6.37.6-0.5-desktop root=/dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO016101NT080JGN-part2 resume=/dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO016101NT080JGN-part1 splash=silent quiet showopts vga=0x345 initrd /boot/initrd-2.6.37.6-0.5-desktop ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 11.4 - 3.0.0-rc5-1 root (hd0,1) kernel /boot/vmlinuz-3.0.0-rc5-1-desktop root=/dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO016101NT080JGN-part2 resume=/dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO016101NT080JGN-part1 splash=silent quiet showopts vga=0x345 initrd /boot/initrd-3.0.0-rc5-1-desktop title openSUSE 11.4 TEST root (hd1,7) kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST9250421AS_5TH05M5Z-part8 resume=/dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO016101NT080JGN-part1 splash=silent quiet showopts initrd /boot/initrd title Windows Vista rootnoverify (hd0,0) chainloader (hd0,0)+1 </pre> 4aea38fd2d10392293d76ecf8f7d9aa77dc13b97 0 350 1215 2011-07-14T17:18:52Z Root 1 Created page with "Since the latest patch you get this error: "icedteanp plugin error: Failed to run /usr/lib/jvm/java-1.6.0-openjdk/jre/bin/java. For more detail rerun "firefox -g" in a termina..." wikitext text/x-wiki Since the latest patch you get this error: "icedteanp plugin error: Failed to run /usr/lib/jvm/java-1.6.0-openjdk/jre/bin/java. For more detail rerun "firefox -g" in a terminal window." The resolution is this: In the following directory type the following for 32 bit: host:/usr/lib/jvm # ln -s java-1.6.0-openjdk-1.6.0/ java-1.6.0-openjdk 64 bit: host:/usr/lib64/jvm # ln -s java-1.6.0-openjdk-1.6.0/ java-1.6.0-openjdk See also bugzilla report #704814 on [[bugzilla.novell.com]] 7a8a00e4db2df687ba3be2cb340b192e27eeaf18 0 80 1228 684 2011-07-20T08:10:14Z Root 1 wikitext text/x-wiki MyBackup - to backup your files like just before an upgrade! *[[tethering or how to use your android as an internet modem]] *[[How to enter system recovery on HTC Hero]] 1a50ef857f84be903b0415ab606df5b0a09fd80d 0 352 1229 2011-07-20T08:11:30Z Root 1 Created page with "Boot into system recovery by holding [HOME] & [POWER]. Then at the red triangle screen press [VOLUP] & [POWER]" wikitext text/x-wiki Boot into system recovery by holding [HOME] & [POWER]. Then at the red triangle screen press [VOLUP] & [POWER] 16fbe950c60ecb1e9084fd04839de686fd7f1fdb 0 353 1232 1231 2011-07-24T17:00:40Z Root 1 wikitext text/x-wiki *[[partitions hpspil]] c600ac2ad96c16c2195f7e550c8064199842ef50 0 354 1236 1235 2011-07-24T20:09:04Z Root 1 wikitext text/x-wiki /dev/sda 112 gb 1 105 gb ntfs 2 7 gb ntfs 1 65 GB ntfs c: windows 4 38 GB ext4 / 3 1 GB swap 2 7 GB ntfs resque 1caba87941ea9904fe7c9aa2f7bf902bf9a807e4 0 366 1251 1250 2011-08-05T08:44:34Z Root 1 wikitext text/x-wiki vcnc {| style="border-spacing:0;" | style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Technical specifications | style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Optical | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| PCVC740K | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| ToUcam Pro | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Sensor | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| CCD | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Pixels | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 640 (H) x 480 (V) | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Still image resolution | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 1280 (H) x 960 (V) | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Illumination | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <nowiki>< 1 lux</nowiki> | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Integrated lens | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| F2.0 | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Resolution/performance | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Output resolution | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Pixels (H x V) | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| <nowiki>Frame rate in frames/sec [fps]</nowiki> |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| VGA | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 640 x 480 | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Up to 30 |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| CIF | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 352 x 288 | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Up to 30 |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| SIF | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 320 x 240 | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Up to 60 |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| QCIF | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 176 x 144 | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Up to 60 |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| QSIF | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 160 x 120 | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Up to 60 |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |- | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| Data format | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| I420, IYUV | style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| |} 03e6bea55b999c2282229fec245b06d506ec1078 0 367 1253 2011-08-10T10:06:44Z Root 1 Created page with "*[[partitions cpu3972]] *[[repos cpu3972]]" wikitext text/x-wiki *[[partitions cpu3972]] *[[repos cpu3972]] aa553f675a5fc5446d326882265e1792e1af286d 0 368 1254 2011-08-10T10:07:10Z Root 1 Created page with "<pre> # | Alias | Name | Enabled | Refresh | URI ..." wikitext text/x-wiki <pre> # | Alias | Name | Enabled | Refresh | URI ---+------------------------------+---------------------------------------------+---------+---------+-------------------------------------------------------------------------------------------------- 1 | download.opensuse.org-webcam | openSUSE BuildService - Drivers for webcams | Yes | Yes | http://download.opensuse.org/repositories/drivers:/webcam/openSUSE_11.4/ 2 | google-talkplugin | google-talkplugin | Yes | Yes | http://dl.google.com/linux/talkplugin/rpm/stable/x86_64 3 | packman.inode.at-suse | Packman Repository | Yes | Yes | http://packman.inode.at/suse/11.4/ 4 | pvdm-contrib | pvdm-contrib | Yes | Yes | http://download.opensuse.org/repositories/openSUSE:/11.4:/Contrib/standard/ 5 | pvdm-fontsmoothtest | pvdm-fontsmoothtest | Yes | Yes | http://download.opensuse.org/repositories/home:/muzlocker/openSUSE_11.4/ 6 | pvdm-games | pvdm-games | Yes | Yes | http://download.opensuse.org/repositories/games/openSUSE_11.4 7 | pvdm-kde-core | pvdm-kde-core | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Release:/47/openSUSE_11.4/ 8 | pvdm-kde-extra | pvdm-kde-extra | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_47_openSUSE_11.4/ 9 | pvdm-kde-play | pvdm-kde-play | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Unstable:/Playground/KDE_Release_47_openSUSE_11.4/ 10 | pvdm-kde-releasedapps | pvdm-kde-releasedapps | Yes | Yes | http://download.opensuse.org/repositories/KDE:/UpdatedApps/openSUSE_11.4/ 11 | pvdm-kernel | pvdm-kernel | Yes | Yes | http://download.opensuse.org/repositories/Kernel:/stable/standard/ 12 | pvdm-lo | pvdm-lo | Yes | No | http://download.opensuse.org/repositories/LibreOffice:/Unstable/openSUSE_11.4/ 13 | pvdm-soundlibs | pvdm-soundlibs | Yes | Yes | http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.4/ 14 | pvdm-wine | pvdm-wine | Yes | Yes | http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.4/ 15 | pvdm-xorg | pvdm-xorg | Yes | Yes | http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.4/ 16 | repo-11.4-non-oss | openSUSE-11.4 Non-OSS | Yes | No | http://download.opensuse.org/distribution/11.4/repo/non-oss/ 17 | repo-11.4-oss | openSUSE-11.4 OSS | Yes | No | http://download.opensuse.org/distribution/11.4/repo/oss/ 18 | repo-11.4-update | openSUSE-11.4 Updates | Yes | Yes | http://download.opensuse.org/update/11.4/ 8092921befd4c58d54bd96881b1a084de9067c07 0 386 1285 1284 2011-08-23T14:42:21Z Root 1 wikitext text/x-wiki hp.com tydelijk1 uitgebruide ww met CAPS johan(2) en cijfers borderlinx pvdmjoomla uit cijf 780cc1346c1c3f8c6e5618e05c42a882b0a1686e 0 133 1291 1213 2011-09-26T15:14:53Z Root 1 wikitext text/x-wiki Per 1 mei 2010 <pre> /dev/sda 75GB 1 ntfs 16GB windows/C boot 3 swap 1GB 4 extndd 50GB 8 ext3 16GB / SnowyWindOSX 5 ext4 16GB / mounted on /data 6 ext2 200MB /boot <============================ 7 ext4 18GB jolicloud 2 FAT32 8GB windows/D recover </pre> Bovenstaand is in volgorde op de disk. 65b42dc64812954e39e1d3a265c706a5066dbf63 0 389 1293 2011-09-27T14:49:00Z Root 1 Created page with "Verhuis van systeem A naar systeem B. =Inpakken= *boot systeem A vanaf liveCD :(alternatief: boot in single-user-mode) *mount de rootpartitie van systeem A: mount /dev/sda1 /m..." wikitext text/x-wiki Verhuis van systeem A naar systeem B. =Inpakken= *boot systeem A vanaf liveCD :(alternatief: boot in single-user-mode) *mount de rootpartitie van systeem A: mount /dev/sda1 /mnt *mount het medium waarop het archief komt. Vaak automatisch, anders: mount /dev/sdf1 /media *ga naar root van (gemounte) filesysteem cd /mnt *(als je gebruikt maakt van de single-user-mode, dan cd / uiteraard) *pak in: tar --one-file-system -cpf /media/systeem.tar * (-j=compressie) =Uitpakken= *boot systeem B vanaf liveCD *maak nieuwe disk aan, en partitioneer. Bijvoorbeeld: fdisk /dev/sda :denk er ook aan om een swap partitie aan te maken (type 82) *maak bestandssystemen aan: mkfs.ext3 /dev/sda1 mkswap /dev/sda2 etc.... *mount de doelpartitie en de gegevensdrager: mount /dev/sda1 /mnt mount /dev/sdf1 /media *pak het systeem uit: cd /mnt tar -xf /media/systeem.tar (-j als je compressie gebruikt) = Inrichten = *pas /etc/fstab aan, vervang bijvoorbeeld UUID's door apparaatnamen zoals /dev/sda1 /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda2 swap swap defaults 0 0 *verwijder 2 udev regels voor netwerkkaarten en optische drives: rm /mnt/etc/udev/rules.d/70-persistent-cd.rules rm /mnt/etc/udev/rules.d/70-persistent-net.rules :deze worden na booten opnieuw aangemaakt. *pas /mnt/etc/X11/xorg.conf aan of wis deze zodat deze opnieuw wordt aangemaakt. *pas GRUB aan: **pas de 'root=' regel aan **vervang in /mnt/boot/grub/menu.lst UUID's door apparaatnamen zoals /dev/sda1 *mount nu de proc en dev bestandssystemen: mount -t proc none /mnt/proc mount -o bind /dev /mnt/dev *ga dan met chroot naar het nieuwe systeem: chroot /mnt *en installeer grub bootloader: grub-install /dev/sda (exit met CRTL-D) 61cb2900799da27a7c6cf18f2d6b9787e6d8f427 0 390 1300 1298 2011-10-04T17:15:40Z Root 1 wikitext text/x-wiki *[[partitions WeTab]] *[[bootloader WeTab]] *[[repos WeTab]] *[[other WeTab]] 951db187dbe6e5d61c6975413e32b8f7665335ca 0 392 1301 2011-10-04T17:16:43Z Root 1 Created page with "sda6 android-2011-08-28/ initrd.img kernel ramdisk.img system.sfs" wikitext text/x-wiki sda6 android-2011-08-28/ initrd.img kernel ramdisk.img system.sfs 4089758714f33a713717ce49154bd8637ec757bd 0 393 1312 1311 2011-10-15T19:40:20Z Root 1 wikitext text/x-wiki =huidig 14 okt 2011= <pre> default=0 timeout=6 root (hd0,5) splashimage=/grub/android-x86.xpm.gz title Android-x86 2011-08-28 kernel /android-2011-08-28/kernel quiet root=/dev/ram0 androidboot_hardware=tegav2 SRC=/android-2011-08-28 # kernel /android-2011-08-28/kernel quiet root=/dev/ram0 androidboot_hardware=tegav2 acpi_sleep=s3_bios,s3_mode SRC=/android-2011-08-28 initrd /android-2011-08-28/initrd.img title Wetab OS root (hd0,0) kernel /extlinux/vmlinuz quiet root=/dev/sda3 ro title KDE Plasma Active root (hd0,4) kernel /boot/vmlinuz-2.6.38.2-8.26-adaptation-pinetrail quiet root=/dev/sda5 title Android-x86 2011-08-28 (Debug mode) kernel /android-2011-08-28/kernel root=/dev/ram0 androidboot_hardware=tegav2 acpi_sleep=s3_bios,s3_mode DEBUG=1 SRC=/android-2011-08-28 initrd /android-2011-08-28/initrd.img </pre> =ter info= <pre> [root@localhost pvdmatten]# cat /etc/extlinux.conf prompt 1 timeout 5000 default vesamenu.c32 menu autoboot menu hidden menu master passwd $1$psPEZQzt$FckzDRpSCbSdUsTDwk22f1 menu title Welcome to WeTab! menu resolution 1024 768 menu background splash1024.png menu color border 0 #ffffffff #00000000 menu color sel 7 #ffffffff #ffffcc00 menu color title 0 #ffffffff #00000000 menu color tabmsg 0 #ffffffff #00000000 menu color unsel 0 #ffffffff #00000000 menu color hotsel 0 #ffffffff #ffffcc00 menu color hotkey 7 #ffFFCC00 #00000000 menu color timeout_msg 0 #ffffffff #00000000 menu color timeout 0 #ffffffff #00000000 menu color cmdline 0 #ffffffff #00000000 menu color cmdmark 0 #ffffcc00 #00000000 menu color pwdborder 0 #ffffcc00 #00000000 menu color pwdheader 0 #ff393837 #ffffcc00 menu color pwdentry 0 #ffffcc00 #00000000 label wetab-os menu label ^WeTab OS kernel vmlinuz append ro root=/dev/sda3 quiet vga=current console=ttyUSB99 menu default label pvdm menu label ^PvdM kernel chain.c32 append boot 6 label android menu label ^Android kernel android-2011-08-28/kernel # append ro root=/dev/sda6 quiet vga=current console=ttyUSB99 append initrd=android-2011-08-28/initrd.img root=/dev/sda6 rw # menu default label bios menu label ^BIOS Update menu hide kernel memdisk append initrd=biosup.img floppy c=8 s=32 h=64 label Meego kernel vmlinuz-2.6.38.2-8.26-adaptation-pinetrail append ro root=/dev/sda5 quiet vga=current menu default </pre> =grub= <pre>default=0 timeout=6 splashimage=/grub/android-x86.xpm.gz title Android-x86 2011-08-28 root (hd1,0) kernel /android-2011-08-28/kernel quiet root=/dev/ram0 androidboot_hardware=tegav2 acpi_sleep=s3_bios,s3_mode SRC=/android-2011-08-28 initrd /android-2011-08-28/initrd.img title Wetab Os root (hd0,0) kernel /extlinux/vmlinuz root=/dev/sda3 ro title Android-x86 2011-08-28 (Debug mode) kernel /android-2011-08-28/kernel root=/dev/ram0 androidboot_hardware=tegav2 acpi_sleep=s3_bios,s3_mode DEBUG=1 SRC=/android-2011-08-28 initrd /android-2011-08-28/initrd.img 43ee8d833456425ed9ea81e64c16acf818de6d33 0 347 1327 1326 2011-10-26T07:13:25Z Root 1 /* The Case for Doing this On Every Hard Disk */ wikitext text/x-wiki Often when you want to use more than one Operating System on your computer, you run into GRUB issues. When you install an OS, or upgrade an installed OS, problems can occur when the new install overwrites your GRUB setup, leaving you with unbootable OS's. It is possible to correct these issues, but that is an annoying exercise that you will have to repeat every time you update stuff. =chainloader= In order to solve this issue for once and for all, the solution is to make 1 partition the 'master GRUB' partition. This GRUB will contain only so called 'chainloader' commands, pointing to all the 'child' partitions containing the OS's. Those partitions will contain the GRUB's from those OS's. So we create a 2 stage boot process: In this scenario let all the OS's manage their own partitions, and THIS IS IMPORTANT: don't let them update our 'master GRUB' partition. They can update their own GRUB during updates etc. =MBR info= Note that the 'grub-install' method has the added protection of not inadvertantly overwriting your partition table if it had been modified since your last MBR backup. This is because the 512byte MBR sector is actually two parts: #The first 446 bytes is the grub stage1 bootloader (or the windows bootloader after you’ve reinstalled windows and it “helpfully” overwrites grub). #The last 64 bytes is where your partition table is stored. So, if you only want to backup the bootloader in the MBR, remember to change the bs=512 to bs=446. = What You Absolutely Need to Know = In order to use grub to boot a computer, you need to know the following: # The partition containing the kernel # Within that partition, the directory path and filename of the kernel # The partition containing /sbin/init In addition, you might need the partition, path and filename of the initrd file, but usually this is not necessary with grub. {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| <center>'''NOTE'''</center> I have seen cases in which a kernel would kernel panic without an initrd statement, and would boot with it. The interesting thing is, once I got it booting, I could remove the initrd statement, rerun grub's setup, and it would now boot without the initrd statement. If you get kernel panics and it isn't obvious why, don't hesitate to insert an initrd statement. |} Now let's take a look at an example. Imagine a system in which /dev/hda1 is mounted as /boot, and /dev/hda9 is mounted as /. Within /boot the kernel filename is vmlinuz-i686-up-4GB. Now let's answer the four questions: # The partition containing the kernel = /dev/hda1, or (hd0,0) in grub-speak # Within that partition, the directory path and filename of the kernel = /vmlinuz-i686-up-4GB(Remember, /dev/hda1 is mounted directly to /boot, so it contains the kernel directly) # The partition containing /sbin/init is /dev/hda9 In that case, here are the grub commands you would input to boot that system: '''grub> root (hd0,0)''' '''grub> kernel /vmlinuz-i686-up-4GB root=/dev/hda9''' '''grub> boot''' The preceding is usually sufficient to boot a Linux box. The standalone root statement tells the partition containing the kernel. The kernel statement describes the path and filename, ''within the partition containing the kernel'' of the kernel. The argument to the root= argument to the kernel statement tells the partition containing /sbin/init, which of course turns out to be the root partition in the booted system. Be careful of these duelling root keywords. The standalone one is the root as seen from grub, and contains the kernel. The argument to the kernel statement is the root as seen from the fully booted system, and contains /sbin/init. Be careful also of where you use grub partition notation and where you use Linux partition notation. You use grub partition notation ((hd0,0)) everywhere except the root= argument to the kernel statement. In the root= argument you use the Linux partition notation. Note that in Linux notation, the drive starts with a for the first IDE port master, then b for the first IDE port slave, then c for the second IDE port master, and&nbsp; d for the second IDE port slave, on and on throughout your IDE ports. In Linux notation, the partition number within the drive starts with 1. In grub partition notation, the first accessible hard drive is (hd0), the next accessible hard drive (even if it's on the 3rd, 4th or higher IDE port) is (hd1), and so forth. In grub partition notation, the partition number is zero based. Thus: /dev/hda1 is the same partition as (hd0,0) Occasionally you'll need to specify an initrd, although this is rare. If so, after the kernel statement and of course before the boot statement, insert the following: initrd /initrd-i686-up-4GB.img It's absolutely essential that if you do use an initrd statement, that the initrd file you reference must match the kernel you referenced earlier. {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| <center>'''NOTE'''</center> I have seen cases in which a kernel would kernel panic without an initrd statement, and would boot with it. The interesting thing is, once I got it booting, I could remove the initrd statement, rerun grub's setup, and it would now boot without the initrd statement. If you get kernel panics and it isn't obvious why, don't hesitate to insert an initrd statement. |} Another documented way to boot from grub is to put the grub-root in the kernel statement itself instead of as a separate entity: '''grub> kernel (hd0,0)/vmlinuz-i686-up-4GB root=/dev/hda9''' '''grub> boot''' If you do that, you'll need to also specify the grub root ((hd0,0)) on any initrd statement. == Booting Up Foreign Distros == Let's say you're a United States English speaker using grub to bust back into a Knoppix machine that lost its boot loader. The commands discussed previously would put you in Knoppix just fine, but the error messages and even the console keyboard would be German (Deutsch). If you wanted to boot up in American English, you'd add the argument lang=us to the kernel statement, like this: '''grub> kernel (hd0,0)/vmlinuz-i686-up-4GB root=/dev/hda9 lang=us''' '''grub> boot''' or '''grub> root (hd0,0)''' '''grub> kernel /vmlinuz-i686-up-4GB root=/dev/hda9 lang=us''' '''grub> boot''' == The Single Partition Configuration == The preceding example detailed a system with a dedicated /boot partition. Especially in these days of modern bioses that can boot past cylinder 1024, many people don't use a separate partition for /boot. Imagine if the root partition were /dev/hda1, and /boot was just another directory on that partition. In that case, here are the commands you'd use: '''grub> root (hd0,0)''' '''grub> kernel /boot/vmlinuz-i686-up-4GB root=/dev/hda1''' '''grub> boot''' The only difference is here the grub root is the same as the booted system root. = Having Grub Do Your Research For You = Often you know the partition containing the kernel, the kernel directory and name, and which partition mounts to root after boot. In that case booting Linux from grub is trivial. Other times you're not so lucky. Like when you accidentally messed up LILO, or when you or someone else installed Windows, inadvertently overwriting the boot loader on the MBR. That's when you need grub the most, but that's also when you're least likely to know the partition containing the kernel, the partition that will ultimately be root, and the name of the kernel. Luckily,&nbsp; grub can help. Your first step is to find the partition containing the kernel and the partition containing /sbin/init. Now type the following at the grub> prompt: find /sbin/init On a machine with three different Linux OS's installed, the answer would come back something like this: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| grub> '''find /sbin/init''' (hd0,8) (hd0,11) (hd1,11) grub> |} In the preceding example, you've found three different partitions containing /sbin/init: {| style="border-spacing:0;" | style="border-top:0.05pt double #808080;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.053cm;"| Grub partition specification | style="border:0.05pt double #808080;padding:0.053cm;"| Linux partition specification |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.053cm;"| (hd0,8) | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.053cm;"| /dev/hda9 |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.053cm;"| (hd0,11) | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.053cm;"| /dev/hda12 |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.053cm;"| (hd1,11) | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.053cm;"| /dev/hde12Note: I infer that hd1 maps to hde because on this particular machine there are two hard disks, one at hda and one at hde. |} Next, find all partitions containing the kernel. Our first attempt assumes that at least one kernel will have filename vmlinuz.: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| grub> '''find /vmlinuz''' (hd0,0) (hd0,11) (hd1,11) grub> |} Then perform the same search for vmlinuz in a directory called /boot: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| grub> '''find /boot/vmlinuz''' (hd0,11) (hd1,11) grub> |} Here we find only two of the three we found in the first attempt, because on this machine, (hd0,0) is mounted as /boot on one of the OS's. Grub's find command is limited. It can find only regular files, not directories. Usually the entire directory path must be specified, although for some reason it finds a couple /boot/vmlinuz when you use find on /vmlinuz. Don't count on that behavior. Another technique for finding info in grub is to use its file completion feature. Let's say you know the kernel is on (hd0,0) and the kernel file begins with vml. Press the tab key after issuing this partial command: null (hd0,0)/vmlinuz Grub performs file completion much like you see at a Linux command prompt. {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| grub> '''null (hd0,0)/vml'''inuz Possible files are: vmlinuz vmlinuz-2.6.3-7mdk vmlinuz-2.6.3-7mdk-i686-up-4GB vmlinuz-i686-up-4GB grub> |} In the preceding, the word null is not a keyword, but instead a word chosen because it is not a keyword. Instead of "null", you could have used "whatever" or "bogus" or any other non-keyword. Once you get the list, you can complete a little more and then press tab again, just like at a bash prompt. By doing so you minimize the likelihood of transcription errors. Occasionally grub won't easily give you all the necessary information. If you need more information than grub can conveniently provide, boot Knoppix. See Troubleshooters.Com's [http://www.troubleshooters.com/linux/knoppix/index.htm Knoppix Knowhow] site for details. = Making a Full grub Boot Floppy = In this document's first article you created a simple Grub boot floppy without a filesystem. This is adequate to boot a computer, but not to install grub on the computer. Installing grub requires a boot floppy with grub on a filesystem. You can do that on any Linux box on which grub is installed. The following are the steps: <nowiki>[root@mydesk root]# mkfs -t ext2 -c /dev/fd0u1440</nowiki> <nowiki>[root@mydesk root]# umount /dev/fd0</nowiki> <nowiki>[root@mydesk root]# umount /dev/fd0u1440</nowiki> <nowiki>[root@mydesk root]# mkdir /mnt/test</nowiki> <nowiki>[root@mydesk root]# mount /dev/fd0u1440 /mnt/test</nowiki> <nowiki>[root@mydesk root]# mkdir -p /mnt/test/boot/grub</nowiki> <nowiki>[root@mydesk root]# cp /boot/grub/stage1 /mnt/test/boot/grub</nowiki> <nowiki>[root@mydesk root]# cp /boot/grub/stage2 /mnt/test/boot/grub</nowiki> <nowiki>[root@mydesk root]# chmod a-w /mnt/test/boot/grub/stage2</nowiki> umount /dev/fd0u1440 <nowiki>[root@mydesk root]# grub</nowiki> grub> root (fd0) grub> setup (fd0) grub> quit <nowiki>[root@mydesk root]#</nowiki> You now have a bootable grub floppy with which you can boot a computer. One more thing should go on the floppy -- an example menu.lst. The menu.lst file is what brings up a "grub menu", and is vital for actually installing the grub bootloader on another computer. On the computer you need to boot, you can edit the menu.lst file to produce a grub menu on boot, and to actually install grub on the system. Note that the example menu.lst shoud NEVER be copied to the floppy before all the steps listed above this paragraph. Here is a typical session showing how to perform the copy. Note that once again, a mount and unmount must be performed. <nowiki>[root@mydesk root]# mount /dev/fd0u1440 /mnt/test</nowiki> <nowiki>[root@mydesk root]# cp -p /usr/share/doc/grub-doc-0.93/menu.lst /mnt/test/boot/grub/</nowiki> stage1 stage2 <nowiki>[root@mydesk root]# cp -p /usr/share/doc/grub-doc-0.93/menu.lst /mnt/test/boot/grub/menu.lst.example</nowiki> <nowiki>[root@mydesk root]# umount /dev/fd0u1440</nowiki> <nowiki>[root@mydesk root]#</nowiki> = Installing grub From Floppy = Do not perform this exercise until you've practiced the earlier exercises. Knowledge of the operation of the grub command line interface is vital to creating and installing a menu driven grub. {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| <center>'''WARNING'''</center> This exercise walks you through creating a floppy based grub boot floppy on a grub installation on computer 1, and then using that floppy to boot and configure grub on computer 2. It WILL wipe out any existing boot loader from computer 2. Hopefully it will replace that boot loader with grub, but there are no guarantees. In fact, this document addresses only Linux grub setups, so if you have Windows or BSD installed, this document cannot help you recover.Therefore, computer 2 MUST be an experimental computer whose data and OS you can afford to lose. |} In the [http://www.troubleshooters.com/linux/grub/grub.htm#_Making_a_Full_grub_Boot_Floppy Making a Full grub Boot Floppy] exercise you created a boot diskette with stage1, stage2, and an example menu.lst named menu.lst.example. Now it's time to use that floppy on another system. As mentioned in the preceding warning, that other system must be an experimental system whose boot loader you can afford to overwrite, possibly unsuccessfully. Insert the full grub boot floppy in the experimental computer, shut the computer down in an orderly fashion, and reboot the computer. During BIOS boot, make sure the computer's first boot drive is the floppy. It is very likely that the the other system has grub installed. To temporarily move its files aside, do the following: mv /boot/grub /boot/orggrub mv /sbin/grub /sbin/orggrub mv /sbin/grub-install /sbin/orggrub-install Basically, rename directory /boot/grub, and then rename all grub executables. In this way you're simulating a machine that has never had grub installed, yet you can "put back" the files with a couple more renames. However, it is not so simple to "put back" the MBR. The basic procedure is as follows: # Boot from the grub floppy # Copy files from the floppy to /boot/grub on the hard disk # Configure /boot/grub/menu.lst for this computer # Reboot from floppy, and install grub == Boot from the grub floppy == '''grub> root (hd0,0)''' '''grub> kernel /vmlinuz-i686-up-4GB root=/dev/hda9''' '''grub> boot''' As mentioned before, if booting to a foreign language distro, use the appropriate lang= kernel argument so that you can work in your native tongue. If everything went right, your experimental system is now booted. == Copy files from the floppy to /boot/grub on the hard disk == First make sure there's no /boot/grub. If there is, rename it, because you sure don't want to overwrite it just to perform this exercise. Now perform the following commands: mkdir /mnt/test mount /dev/fd0u1440 /mnt/test cp -Rp /mnt/test/boot/grub /boot == Configure /boot/grub/menu.lst for this computer == If you began this document as a grub newbie, the sample menu.lst that ships with grub would have been useless to you. What a difference a few exercises can make. You now know how to boot a computer from the grub> prompt. You know the difference between the grub root and the root directory seen by Linux after bootup. You know how to structure a grub kernel statement. A menu.lst file is basically just the same list of commands you'd use at the grub> prompt, except that the boot command is not included. The example menu.lst has commands for installing operating systems from mach to Windows, and it even has an entry that installs grub on the system and another that changes the menu colors. All of that is extraneous. What you want to do is delete all the non-Linux stuff, and configure the Linux commands to match your experimental machine's kernel partition, Linux root partition, and kernel filename. The following is an example of such an edited example file saved as menu.lst: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| '''<nowiki>#</nowiki>''' '''<nowiki># Sample boot menu configuration file</nowiki>''' '''<nowiki>#</nowiki>''' '''<nowiki># Boot automatically after 30 secs.</nowiki>''' '''timeout 30''' '''<nowiki># By default, boot the first entry.</nowiki>''' '''default 0''' '''<nowiki># Fallback to the second entry.</nowiki>''' '''<nowiki># fallback 1 </nowiki> <nowiki># BE SURE TO COMMENT THIS OUT!!!!!!!!!!!!!!</nowiki>''' '''<nowiki># For booting GNU/Linux</nowiki>''' '''title GNU/Linux''' '''root (hd0,0)''' '''kernel /boot/vmlinuz-2.6.7 root=/dev/hda1 lang=us''' |} A few notes are in order: * BE SURE to comment out the "fallback 1", because there is no choice 1, only a choice 0. * The default 0 statement simply points to which choice will run if the user makes no choice within the timeout period. * The lang= is unnecessary unless you're booting up a foreign distro and want to see it in your native language. * The root (hd0,0) needs to be adjusted to point to the partition containing the kernel. * The root=/dev/hda1 needs to be adjusted to point to the partition that will be mounted as root after booting. Note that it is expressed in Linux notation, not in grub notation. * The kernel statement points to the kernel ''relative to the grub root.'' In the preceding file it points to /boot/vmlinuz-2.6.7 in the Linux root partition. If Linux used a partition just for /boot, and that partition were /dev/hda1 as is typical of boot partitions, then the kernel would point to&nbsp;/vmlinuz-2.6.7 instead of /boot/vmlinuz-2.6.7, because the file would be on the root of the boot partition, and would become subservient to /boot only after the partition is mounted by Linux. * Grub's default menu file is /boot/grub/menu.lst. You can use a different file, but it would require jumping through quite a few hoops. Use the default. * None of this is new to you. You already did all of this at the grub> prompt in previous exercises. Your /boot/grub/menu.lst file is now complete. If you created it correctly, you can now install grub from your floppy: == Reboot from floppy, and install grub == Insert your full grub boot floppy in the experimental machine, and reboot. The machine boots to the floppy, and you are presented with the grub> prompt. From there, installation is easy, assuming you've done the previous steps correctly: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| '''grub> root (hd0,0)''' '''grub> setup (hd0)''' '''grub> reboot''' |} The machine reboots again, and if you remove the floppy, you are presented a 1 item grub menu. This is what it looks like: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| [[Image:gnulinuxmenu.gif]] |} Pressing Enter on that item boots the kernel listed in your menu.lst. A few notes are in order: * Never remove the floppy while the floppy light is on * If you fail to remove the floppy before the reboot reaches the bootloader, it will boot from floppy again. In that case, just boot from floppy as you have in prior exercises, and then remove the floppy and reboot the machine to get the menu. == Summary == Thats it. You created a bootable floppy with stage1, stage2 and an example menu file, and used that floppy to install a grub bootloader on a machine. This is how you can take a machine with a blown bootloader and configure it to boot with grub. However, your "grub installation" falls short. None of the grub executables are there: * grub * grub-floppy * grub-install * grub-md5-crypt * grub-reboot grub-terminfo Also, many files normally placed in /boot/grub are not there: * device.map * e2fs_stage1_5 * jfs_stage1_5 * minix_stage1_5 * reiserfs_stage1_5 * xfs_stage1_5 The other thing you don't have is the documentation that usually comes in /usr/share/grub.Once you get the machine booting in a stable manner, you'll probably want to install grub from a package manager or by compiling the source. Be sure to back up your existing /boot/grub/menu.lst. = Working With a Fully Installed grub = You don't want to reboot to floppy just to get to a grub> prompt or to make changes to the bootloader on your MBR. Once you've installed the full grub package you don't need to. You can use grub-install to install a newly configured boot loader without resorting to your boot floppy. You can use grub to view the results of a new menu.lst. After you've installed grub (or restored the original installation by undoing the renames), edit your menu.lst , insert a second entry that boots the 2.4 kernel instead of the 2.6, name each entry for its kernel number, and restore the. Here is the resulting file: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| '''<nowiki>#</nowiki>''' '''<nowiki># Sample boot menu configuration file</nowiki>''' '''<nowiki>#</nowiki>''' '''<nowiki># Boot automatically after 30 secs.</nowiki>''' '''timeout 30''' '''<nowiki># By default, boot the first entry.</nowiki>''' '''default 0''' '''<nowiki># Fallback to the second entry.</nowiki>''' '''fallback 1 ''' '''<nowiki># For booting GNU/Linux</nowiki>''' '''title 26''' '''root (hd0,0)''' '''kernel /boot/vmlinuz-2.6.7 root=/dev/hda1 lang=us''' '''<nowiki># For booting GNU/Linux</nowiki>''' '''title 24''' '''root (hd0,0)''' '''kernel /boot/vmlinuz-2.4.27 root=/dev/hda1 lang=us''' |} The preceding file has two boot choices: One for the 2.6 kernel (appropriately named 26) and one for the 2.4 kernel (appropriately named 24). It defaults to 26, but if for some reason 26 won't boot it falls back to 24. Once the file is saved, perform the following command: grub-install /dev/hda1 {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| <center>'''NOTE'''</center> To get the same result, you can also run grub, either from a command line or via a grub boot floppy, and perform the following command sequence: grub> root (hd0,0) grub> setup (hd0) The preceding assumes that the kernel is located on (hd0,0), which is otherwise known as /dev/hda1, and that you're installing it to the MBR of the first hard disk, also known as /dev/hda. |} The next time you boot your computer, you'll see choices 26 and 24, and they'll do the right thing, as follows: If you want to view the menu without rebooting, try this command: grub --config-file \(hd0,0\)/boot/grub/menu.lst In the preceding, note that you need to escape the parentheses of the grub partition because otherwise the shell will interpret those parentheses as special characters. Perform that command and you'll see the menu, which looks like the following: {| style="border-spacing:0;" | style="border:0.05pt double #808080;padding:0.053cm;"| [[Image:26and24menu.gif]] |} However, you cannot actually boot from grub run on the command line. == Options from the grub menu == We all hope every item on the menu produces a clean boot. If not, you can either edit individual commands in a given menu choice by pressing the&nbsp; e key, or drop down to the grub command prompt by pressing the c key. Generally speaking, you edit commands if you suspect the menu choice is close to a correct configuration, and you drop directly to the grub command prompt if you suspect the menu item to be totally wrong, or if you need the facilities of grub's find command or its command completion feature. = Why Dedicated? = If you've ever had four or more Linux distros on one box, you already know the answer. Install a new distro, and you lose the ability to boot the others. Oh sure, some distros are nice enough to try to detect the others, but often label them wrong. Some distros don't even try, but assume they're the only distro on the disk. Some distros overwrite everything with LILO. When installing, removing and tweaking&nbsp;multiple distros on a single box, what you really need is a single menu of all boots. Ideally, you don't want that menu associated with a distro, because it it were, it would be overwritten every time you remove or reinstall that distro. This document walks you through creating a 1 MB hard disk partition containing the grub boot code and the grub menu for all your various boots. By keeping this one and only one menu up to date, you avoid the confusion of constantly having to re-import all other boots every time you install something new. Because the partition is only a single megabyte, you avoid the temptation to cannibalize it for something else. Once your grub partition is in place, adding a distro is as simple as installing that distro, then mounting the grub partition, and adding the new distro's grub boot information (menu.lst) to the boot distro's menu.lst, and then resetting the hard disk MBR to point to the grub partition. = Creating Your Grub Partition = Unless you have very strange hardware with special booting needs, you can fit all Grub code into a 1MB partition. Create the partition with fdisk. The fdisk program is able to make tiny partitions not on cylinder boundaries. Other programs such as cfdisk round to the nearest cylinder boundary, thereby making this partition much bigger than it needs to be. For the same reason, use fdisk to create the partition after this one, to make sure that no space is left in the middle. From then on, assuming partitions are big, other partitioning programs are fine, because a few megabytes on one side or the other of a 2GB partition aren't significant. If you're working with a very old bios with the ancient 1024 cylinder limitation, it should be very near the front of the disk (make it /dev/hda1). Remember, it's only a megabyte in size, so it's not going to "push out" any other partitions with this limitation (typically the /boot partition). As a practical matter, modern bios implementations don't have this limitation, so on modern machines you can put the grub partition anywhere. Try to make sure to remember the device number (/dev/hda1) or whatever) housing the grub partition. However, if worst comes to worst, you can quickly see which partition using this command: fdisk -lu /dev/hda The preceding command prints out the number of sectors used by each partition. The Grub partition will be the smallest, because no modern operating system can be housed in a 1MB partition. Once you've used fdisk to create the partition, format it with the mkfs.ext2 command. There's no use making this an ext3 partition, because it's small enough to fsck anyway. = Setting Up Your Grub Partition = This is simply a matter of copying files. At the very least, you must have these three files: # stage1 # stage2 # menu.lst You can copy stage1 and stage2 from the /boot/grub directory of the booted OS, or any partition. However, if you have any unusual hardware or journaling file systems besides ext3, you'll need some of the "stage1_5" files. In such a case, ALL the stage files must be copied from the same source. On your currently booted distro, perform the following command: locate stage Here are some of the files that command shows on my Mandriva 2006 system: * /lib/grub/i386-mandriva/iso9660_stage1_5 * /lib/grub/i386-mandriva/e2fs_stage1_5 * /lib/grub/i386-mandriva/fat_stage1_5 * /lib/grub/i386-mandriva/ffs_stage1_5 * /lib/grub/i386-mandriva/reiserfs_stage1_5 * /lib/grub/i386-mandriva/jfs_stage1_5 * /lib/grub/i386-mandriva/minix_stage1_5 * /lib/grub/i386-mandriva/stage2_eltorito * /lib/grub/i386-mandriva/stage1 * /lib/grub/i386-mandriva/stage2 * /lib/grub/i386-mandriva/ufs2_stage1_5 * /lib/grub/i386-mandriva/vstafs_stage1_5 * /lib/grub/i386-mandriva/xfs_stage1_5 I could copy ALL those files to the grub partition, or just stage1 and stage2.Here's how I'd do it: mkdir /mnt/test mount /dev/hda1 /mnt/test mkdir -p /mnt/test/boot/grub cp -p /lib/grub/i386-mandriva/* /mnt/test/boot/grub Note that on my system, a du command reveals that all those files consume only 376KB, so there's plenty of room. The only thing left to do is create /mnt/test/boot/grub/menu.lst. = Making Your menu.lst = If possible, find a partition whose menu.lst contains choices for booting several different partitions. If the partition having such a menu.lst were /dev/hda7 and your Grub partition were /dev/hda1, and you mounted them as /mnt/hda1 and &nbsp;/mnt/hda7, you'd perform the following command: cp /mnt/hda7/boot/grub/menu.lst /mnt/hda1/boot/grub Now that you have a starter for menu.lst, edit the file and pull in the info from menu.lst files from other partitions, straight into your editor. In each case, delete out the new global information and keep only the info for each new boot. Be careful that you don't get two different choices for essentially the same boot. Occasionally, on LILO-only distributions, you might find no menu.lst file. In that case, import that distro's /etc/lilo.conf and translate LILO menu info to Grub menu info. It's not difficult if you do it slowly. As you edit the file, make different versions so that if it doesn't work you can try a simpler version. = Making it Happen at Boot Time = You've made your menu.lst on your Grub partition, complete with boot info from every distro on the system. The trouble is, that menu file won't be consulted at boot time. To get the boot to consult it, you need to tell the hard disk's MBR to consult your Grub partition. Assuming your Grub partition is /dev/hda1, here's how you do it: <nowiki># grub</nowiki> grub> root (hd0,0) grub> setup (hd0) grub> quit <nowiki># reboot</nowiki> In the preceding command sequence, the first runs the grub executable. The second sets the root to (hd0,0), which is grub-speak for /dev/hda1. The third command tells grub to install code on the MBR that looks to /dev/hda1 for boot code. The fourth command terminates the grub command, and the fifth reboots the computer. When the computer reboots, if all went well you should see the menu you set up on your grub partition. If not, troubleshoot. If need be, bust back into the machine using the Grub techniques on the [http://www.troubleshooters.com/linux/grub/grub.htm Grub From the Ground Up] page, using either a Grub floppy or a Knoppix CD. = Adding a New Distro = This is where you start to see the real benefit of the dedicated Grub partition. In the bad old days, installing one more distro on your hard disk would necessitate a long and difficult search for other boots, culminating in voluminous troubleshooting. Now you simply edit your Grub partition's menu.lst and add the boots (not the globals) from the latest distro addition. Booted into the latest distro, signed in as root, it would go something like this: # Mount /dev/hda1 /mnt/test # cd /mnt/test/boot/grub # cp -p menu.lst menu.lst.bup # vim menu.lst # Within vim: ## G &nbsp;to get to the bottom ## <nowiki>o&nbsp;<Enter><Enter><Enter><Enter> (in order to open a space) </nowiki> ## :r /boot/grub/menu.lst ### NOTE: If the new version had /etc/lilo.conf and no /boot/grub/menu.lst, you might need to read in lilo.conf and then translate. It's not particularly difficult. ## Delete all global info brought in by the new menu.lst, and also any boots you don't need. ## :wq # Run Grub, and within Grub do this: ## grub> root (hd0,0) ## setup (hd0) # Reboot the computer, and your list should include all old boots as well as those brought in by the new boots. = The Case for Doing this On Every Hard Disk = A tiny dedicated Grub partition makes it easy to include a [http://www.troubleshooters.com/linux/knoppix/knoppix_partition.htm dedicated Knoppix partition], along with anything else you might need on the hard drive. I find life much easier with a Knoppix partition on every hard disk I own. On dedicated data drives, it allows me to grab my data if my system drive should become defunct. It allows easy transfer of data between an old data disk and its replacement, either with the old disk still in the production computer and the new disk in a spare computer, or the new disk in the production computer and the old disk in the spare computer (in other words, you forgot to do it before shutting down the production computer with the old disk -- it happens). You never know when somebody, some time, will dual or tri-boot the system. Or install six different OS's on it. Having a dedicated Grub partition makes such events&nbsp;much easier to handle. 10f89d155c2e737439d341aec21f14417cda70d5 0 394 1330 1316 2011-11-11T11:13:01Z Root 1 wikitext text/x-wiki <pre> cpu3972:/home/pvdm # fdisk -l Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x7e407e40 Device Boot Start End Blocks Id System /dev/sda1 63 81931499 40965718+ 7 HPFS/NTFS/exFAT /dev/sda2 81931500 123877213 20972857 7 btrfs <== openSUSE 12.1 /dev/sda3 * 123877376 488396799 182259712 f W95 Ext'd (LBA) /dev/sda5 123879424 124278783 199680 83 Linux <== boot; MBR wijst ook hier naar toe. MASTER grub /dev/sda6 124280832 128471039 2095104 82 Linux swap / Solaris /dev/sda7 128473088 170418175 20972544 83 Linux <== openSUSE 11.4 / /dev/sda8 170420224 488376319 158978048 83 Linux <== data cpu3972:/home/pvdm # mount | grep sda | sort /dev/sda1 on /windows/C type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sda2 on /windows/D type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sda5 on /boot type ext2 (rw,relatime,user_xattr,acl,barrier=1) <== NOT MEER GEMOUNT /dev/sda7 on / type ext4 (rw,noatime,user_xattr,acl,barrier=1,data=ordered) /dev/sda8 on /data type ext4 (rw,noatime,user_xattr,acl,barrier=1,data=ordered) </pre> d4ff5fe49066a6c42928a7662da1ba242cb1c428 0 398 1349 1348 2011-11-14T17:23:59Z Root 1 /* Re-using an SSD */ wikitext text/x-wiki When you want to install Linux to an SSD, there are a lot of things to think about. This wiki post will look at all those things. =1. start your partitons on a 4k boundary= Because SSD's use 'blocks' of 4k in size, you must line up the partition boudaries on a block boudary for the best performance. In fact, it is even better to start your partitons on a '''512k''' block boundary. To do that, start fdisk with the parameters ''''-H 32 -C 32 -c'''' and create a completely new partitiontable. fdisk -H 32 -C 32 -c '''Note: Intel SSD's uses smaller blocks so use a different command: fdisk -H 16 -S 16 -c''' =2. Optimize I/O= To adjust the stripe width and stride of an EXT4 filesystem, use this command to create a new filesystem: mkfs.ext4 -E stride=128,stripe-width=128 /dev/sdaX where sdaX is of course your ssd partition. To tune an already existing filesystem, you can use: tune2fs -E stride=128,stripe-width=128 /dev/sdaX '''Intel''' users should use the value '''32''' for the stripe width ==Use a different scheduler== You can also use a different i/o scheduler, the deadline scheduler, because the one that is used as a standard in the kernel is optimized for magnetic hard drives. Modify /etc/rc.local (or /etc/rc.d/boot.local on '''openSUSE''') and insert just before 'exit 0' echo deadline > /sys/block/sda/queue/scheduler =3. Use TRIM= 3.1 first, check if your SSD supports the TRIM command hdparm -I /dev/sda | egrep "Enabled|TRIM" 3.2 second, your kernel needs to be > 2.6.33 uname -r 3.3 without special mount options, TRIM will not be used. To enable TRIM, use the 'discard' mount option in /etc/fstab. /dev/sdaX / ext4 discard,etc. etc. etc....... Also, you can use the noatime option to minmize the wear on the disk, so that would make the fstab line: /dev/sdaX / ext4 noatime,discard,etc. etc. etc....... =Re-using an SSD= On occasion, users may wish to completely reset an SSD's cells to the same virgin state they were manufactured, thus restoring it to its factory default write performance. Write performance is known to degrade over time even on SSDs with native TRIM support. When you want to reformat an SSD, it is best to completely wipe the disk. That way the algorithm will also be reset to get the best possible performance in your new configuration. To do that, you can use hdparm XXXX to be added.. XXXXXXX =Further performance enhancements= To increase system performance and to eliminate unnecessary write actions to the SSD, you can use a RAM disk. Add this line to /etc/fstab: tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 50d18be86b8c378252c07451d02763163e97283a 0 125 1351 956 2011-11-24T12:52:20Z Root 1 wikitext text/x-wiki Per 1 augustus 2010 <pre> /dev/sda (SDD-80GB) Device Boot Start End Blocks Id System /dev/sda1 2048 4208639 2103296 82 Linux swap / Solaris swap /dev/sda2 * 4208640 46153727 20972544 83 Linux / /dev/sda3 46153728 156301311 55073792 83 Linux /home /dev/sdb (HDD-250GB) Device Boot Start End Blocks Id System /dev/sdb1 63 62637434 31318686 7 HPFS/NTFS/exFAT /dev/sdb2 467419136 469506047 1043456 c W95 FAT32 (LBA) /dev/sdb3 469507849 488386312 9439232 7 HPFS/NTFS/exFAT /dev/sdb4 * 62637435 467411174 202386870 5 Extended /dev/sdb5 62637498 66734009 2048256 82 Linux swap / Solaris swap /dev/sdb6 66734073 333059579 133162753+ 83 Linux /data /dev/sdb7 333059643 406444499 36692428+ 83 Linux / oude 11.3 mag weg /dev/sdb8 406444563 467411174 30483306 83 Linux / openSUSE 12.1 1 ntfs 4 extended 5 swap 6 ext4 /data 7 ext4 / opensuse 11.3 productie 8 ext4 / opensuse 11.4 testing (factory) 2 fat32 HP_TOOLS 3 ntfs HP_RECOVERY </pre> b36775771179808bf8dc3a81f1fa3d901ce1a924 0 400 1370 1369 2011-12-05T15:48:38Z Root 1 wikitext text/x-wiki On openSUSE 12.1, when you configure VLC to use the qt interface (this has to be done in the 'show settings: all' view) it simply crashes. When you start it again, it crashes again during start. Being unable to disable this again, this leaves you with an unworkable VLC. To disable qt interface, go to your ~/.config/vlc> directory, open vlcrc file and put an '#' before the line 'extraintf=qt4' 8aade9920ac177f3580ef916c1109093d1b49c9d 0 401 1378 1377 2011-12-08T10:58:41Z Root 1 wikitext text/x-wiki ===Retail=== [[File:Northumberlad Street, Newcastle upon Tyne.jpg|thumb|Looking south along [[Northumberland Street]] in July 2006]] In 2010, Newcastle was positioned ninth in the retail centre expenditure league of the UK. There are several major shopping areas in Newcastle city centre. The largest of these is the [[Eldon Square Shopping Centre]], one of the largest city centre shopping complexes in the UK. It incorporates a flagship [[Debenhams]] store as well as one of the largest [[John Lewis Newcastle|John Lewis]] stores in the UK. John Lewis is still known to many in Newcastle as Bainbridges which according to sources was one of the first department stores in the world. Eldon Square is currently undergoing a full redevelopment. A new bus station, replacing the old underground bus station, was officially opened in March 2007. The wing of the centre, including the undercover Green Market, near Grainger Street was demolished in 2007 so that the area could be redeveloped. This was completed in February 2010 with the opening of a flagship [[Debenhams]] department store as well as other major stores including [[Apple store|Apple]], [[Hollister Co.|Hollister]] & [[Guess (clothing)|Guess]]. The main shopping street in the city is [[Northumberland Street]]. In a 2004 report, it was ranked as the most expensive shopping street in the UK for rent, outside of London. It is home to two major department stores including the first and largest [[Fenwick (department store)|Fenwick]] department store, which houses some of the most luxurious [[designer labels]], and one of the largest [[Marks and Spencer]] stores outside London. Both stores have entrances into Eldon Square Shopping Centre. Other shopping destinations in Newcastle include Grainger Street and the area around [[Grey's Monument]], the relatively modern Eldon Garden and [[Monument Mall]] complexes, the Newgate Centre, [[Central Arcade]] and the traditional [[Grainger Market]]. Outside the city centre, the largest suburban shopping areas are [[Gosforth]] and [[Byker]]. The largest [[Tesco]] store in the United Kingdom is located in [[Kingston Park]] on the edge of Newcastle. Close to Newcastle, the largest indoor shopping centre in Europe, the [[MetroCentre (shopping centre)|MetroCentre]], is located in [[Gateshead]]. 847689c6a09d3cd34b591cd86d0f60eef4a394b4 0 402 1387 1386 2011-12-13T10:11:28Z Root 1 wikitext text/x-wiki When I was upgrading my wikis to version 1.18, I encountered several problems. I resolved those problems, and to help users who run into the same issues I will document the solution here. =First problem: after upgrading, the URL http://<site>/mw-config/index.php does not work= When you, as per instruction in the UPGRADE readme file, browse to the URL http://<site>/mw-config/index.php, it does not show up. If you look into the apache error log, you will find entries like PHP Fatal error: Cannot redeclare wfprofilein() (previously declared in /srv/www/htdocs/wiki/includes/profiler/Profiler.php:14) in /srv/www/htdocs/wiki/includes/ProfilerStub.php on line 24 This can be fixed by editing the file 'StartProfiler.php' in your wiki root. =Second problem: If you have FCKeditor, you get PHP Fatal error: Call to undefined method Parser::strip() in /srv/www/htdocs/wiki/extensions/FCKeditor/FCKeditor.body.php= For some reason, this new wiki does not like the installed FCKeditor. So I commented the line in LocalSettings.php: // Use the FCK editor #require_once("$IP/extensions/FCKeditor/FCKeditor.php"); =Further problems= I had several other problem, among them errors that the update could not create several tables. It mentioned that it had problems with the CHARCTERSET. I resolved that by manually creating these tables on the mysql CLI, using UTF8 as CHARACTERSET. Unfortunately, the second time I was doing this update, these errors did not occur, so I could not document them here. 93ecbb8fd1cf9bb7f489427e33b96ab40317aa37 0 132 1399 1398 2011-12-17T16:47:28Z Root 1 wikitext text/x-wiki *[[partitions akoya]] *[[hwinfo akoya]] ff73cb09b9551c64729eeb16aa6dd9444be76769 0 403 1400 2011-12-17T16:48:01Z Root 1 Created page with "wireless: RT2860 Ralink" wikitext text/x-wiki wireless: RT2860 Ralink 34aa38fa58ced5bab06d12556a55147c21c24ea2 0 131 1413 1409 2011-12-29T12:07:56Z Root 1 wikitext text/x-wiki To capture video from a firewire device use: dvgrab -frames 0 -size 0 -format raw -noavc -showstatus -csize 1000 tape dvgrab -frames 0 -size 0 -format dv2 -noavc -showstatus -csize 1000 tape dvgrab -size 0 -format best options: dvgrab -autosplit -frames 0 -size 0 -format raw -noavc -showstatus -timestamp tape where -frames number max number of frames per split 0 = unlimited [default 0] -size number max file size, 0 = unlimited [default 1000] -csize number split file when collections of files are about to exceed number MiB, 0 = unlimited [default 0] -format type save as one of the following file types [default raw] raw raw DV file with a .dv extension dif raw DV file with a .dif extension dv1 'Type 1' DV AVI file dv2, avi 'Type 2' DV AVI file qt, mov QuickTime DV movie mpeg2, hdv MPEG-2 transport stream (HDV) jpeg, jpg sequence of JPEG files (DV only) -noavc disable use of AV/C VTR control -srt generate .srt subtitle files containing the recording date and time in SRT format. -t, -timestamp Put information on date and time of recording into file name. -a, -autosplit[=num] Try to detect whenever a new recording starts, and store it into a separate file. This can be combined with the -frames and -size options, and a split occurs whenever a specified event arises. Autosplit is off by default. tape is the filename =Format types:= <pre> raw Input #0, dv, from 'test-raw001.dv': Duration: 00:00:29.12, start: 0.000000, bitrate: 28800 kb/s Stream #0.0: Video: dvvideo, yuv420p, 720x576, 28800 kb/s, PAR 16:15 DAR 4:3, 25 tbr, 25 tbn, 25 tbc Stream #0.1: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s dv1 Input #0, avi, from 'test-dv1001.avi': Duration: 00:00:29.08, start: 0.000000, bitrate: 30336 kb/s Stream #0.0: Video: dvvideo, yuv420p, 720x576, 28800 kb/s, PAR 16:15 DAR 4:3, 25 tbr, 25 tbn, 25 tbc Stream #0.1: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s dv2 Input #0, avi, from 'test-dv2001.avi': Duration: 00:00:27.64, start: 0.000000, bitrate: 30345 kb/s Stream #0.0: Video: dvvideo, yuv420p, 720x576 [PAR 16:15 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Stream #0.1: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s </pre> c30b040d01aac4b4b9ccbf4e3695959e691a1813 0 404 1418 2012-01-03T17:44:06Z Root 1 Created page with "Eisen aan nieuwe netbook: *usb 3.0 poorten, genoeg en positie *firewire *toetsenbord verlichting of led lampje *SD ingang *SSD enabled *middle mousekey" wikitext text/x-wiki Eisen aan nieuwe netbook: *usb 3.0 poorten, genoeg en positie *firewire *toetsenbord verlichting of led lampje *SD ingang *SSD enabled *middle mousekey de0728cb28e6d1e8c14b9e8280857acf4e6f9bd6 0 22 1433 1431 2012-01-20T10:29:50Z Root 1 wikitext text/x-wiki * Herrie http://www.herrie.info commandline mp3 player/jukebox * Thunder & Lightning 3D war simulator http://tnlgame.net * WeedIt File duplicate scanner http://adm1n.cjb.net/cw * Bacula http://www.bacula.org * MyRPM Create RPMs without fuss http://code.google.com/p/myrpm * RockBox Open source firmware replacement for many popular MP3 players * http://bluemarine.tidalwave.it/ An open source application for the digital photo workflow * http://www.linux.com/articles/57222 tesseract en other OCR meuk * http://groundstate.ca/ocr ocropus * http://www.openfiler.com opensource NAS * http://www.andlinux.org/ run linux from within wondows * http://www.ossec.net/ OSSEC is an Open Source Host-based Intrusion Detection System. It performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response * http://www.jokosher.org/ jokosher audio editor * Zenmap graphical interface for nmap * slowloris apache killler * Unetbootin install any os on usb stick * http://pianoteq.com piano synthesizer * http://luma.sourceforge.net -> graphical LDAP browser * [[http://www.php-web-statistik.de/index-english.html]] php webstat * [[http://download.bitdefender.com/SMB/Workstation_Security_and_Management/BitDefender_Antivirus_Scanner_for_Unices/Unix/Current/EN_FR_BR_RO/Linux/ bitdefender antivirus scanner]] * [[http://kde-apps.org/content/show.php/Hydrogen?content=14152 Hydrogen KDE Sound Application]] *[[http://www.jolicloud.com jolicloud, netbook OS]] *[[http://www.openvas.org openvas, fork from nessus]] *[[http://www.roomle.com roomle, online woninginrichting]] *[[gbrainy brain trainer]] *[[typolight lightweight CMS]] 1ed64afddcbf7285330b881a6e5f9d1ba5402187 6 407 1436 2012-01-26T14:15:32Z Root 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 408 1437 2012-01-26T14:15:59Z Root 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 409 1438 2012-01-26T14:17:06Z Root 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 124 1442 1258 2012-01-26T14:44:19Z Root 1 wikitext text/x-wiki *[[specs lap088]] *[[partitions]] *[[grub]] *[[repos]] 66b97818e64f394a37ef9ba618e19b0e0adb15ae 0 410 1444 1443 2012-01-26T14:49:44Z Root 1 wikitext text/x-wiki == Specificaties HP EliteBook 8530p == {| style="border-spacing:0;" | style="border:none;padding:0.0194in;"| | colspan="2" style="border:none;padding:0.0194in;"| '''Algemeen''' |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Merk | style="border:none;padding:0.0194in;"| HP |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Productnaam | style="border:none;padding:0.0194in;"| EliteBook 8530p |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Productcode | style="border:none;padding:0.0194in;"| VC221EA |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| EAN code | style="border:none;padding:0.0194in;"| 0884962339817 |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Toegevoegd op | style="border:none;padding:0.0194in;"| donderdag 09 juli 2009 |} {| style="border-spacing:0;" ! ! Processor / Chipset / Geheugen ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Processor - Type | style="border:none;padding:0.0194in;"| Intel Core 2 Duo P8800 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Processor - Klokfrequentie | style="border:none;padding:0.0194in;"| 2,66 GHz | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Chipset | style="border:none;padding:0.0194in;"| Intel PM45 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Geheugen capaciteit | style="border:none;padding:0.0194in;"| 2 GB | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Type geheugen | style="border:none;padding:0.0194in;"| DDR2 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| SODIMM sloten | style="border:none;padding:0.0194in;"| 2 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Geheugen uitbreidbaar tot | style="border:none;padding:0.0194in;"| 8 GB | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Graphics ! colspan="3" | <div align="left">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Type videokaart | style="border:none;padding:0.0194in;"| ATI Mobility Radeon HD 3650 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Videogeheugen - Hoeveelheid | style="border:none;padding:0.0194in;"| 256 MB | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Scherm - Afmeting | style="border:none;padding:0.0194in;"| 15,4 inch | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Scherm - Resolutie | style="border:none;padding:0.0194in;"| 1680x1050 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| DVI-uitgang | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| VGA-uitgang | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| HDMI-uitgang | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Opslag ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Harddisk/SSD - Capaciteit | style="border:none;padding:0.0194in;"| 250 GB | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Harddisk/SSD - Toerental | style="border:none;padding:0.0194in;"| 7.200 rpm | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| DVD branden | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Connectiviteit ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| LAN - Snelheid | style="border:none;padding:0.0194in;"| 1.000 Mbit/s | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| WLAN - Standaard | style="border:none;padding:0.0194in;"| 802.11n | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Modem | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Bluetooth | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Infrarood | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| HSDPA/UMTS | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Audio ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Geïntegreerde microfoon | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Aansluitingen ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| PC-Card Type II | style="border:none;padding:0.0194in;"| 0 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Smartcard | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| USB 2.0 | style="border:none;padding:0.0194in;"| 4 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| FireWire - Totaal | style="border:none;padding:0.0194in;"| 1 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| eSATA | style="border:none;padding:0.0194in;"| 1 | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Aansluiting dockingstation | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Overige Hardware ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Ingebouwde webcam | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Maten en gewichten ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Gewicht - Incl. accu | style="border:none;padding:0.0194in;"| 2,86 kg | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Afmeting - Breedte | style="border:none;padding:0.0194in;"| 35,5 cm | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Afmeting - Diepte | style="border:none;padding:0.0194in;"| 26,3 cm | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} {| style="border-spacing:0;" ! ! Software ! colspan="3" | <div align="right">Zoek producten op basis van specificatie</div> |- | style="border:none;padding:0.0194in;"| &nbsp; | style="border:none;padding:0.0194in;"| Besturingssysteem | style="border:none;padding:0.0194in;"| Microsoft Windows Vista Business | style="border:none;padding:0.0194in;"| | style="border:none;padding:0.0194in;"| |} 367e3cfa181f3db82373aac481b4da1a858c2b7c 0 144 1446 1445 2012-01-26T15:09:32Z Root 1 wikitext text/x-wiki Thunderbird seems to always start firefox when a link is clicked. This is bad behaviour. The following command will start chromium: gconftool-2 --type string -s /desktop/gnome/url-handlers/http/command "/usr/bin/chromium %s" This works also in KDE other solution: jan 2012 Nothing helped, so I've found other solution: 1) in Thunderbird go to Edit -> Preferences -> Advanced -> General -> Configuration Edito 2) change network.protocol-handler.warn-external.http and network.protocol-handler.warn-external.https to "true" 3)Click on any link in tb 4) navigate to /usr/bin/google-chrome 5) have fun e2f25e088a9ead0d39be684650123bfc9391d82d 0 399 1456 1381 2012-02-10T08:03:12Z Root 1 /* For multimedia stuff & codecs: */ wikitext text/x-wiki This guide is a summary of the steps I take to customize a default installation of openSUSE. This particular guide was rewritten for openSUSE 11.2, but most stuff should be applicable to other versions as well. ==first: repos== first, type # zypper lr -d *delete '''source''' and '''debug''' repos and '''installation dvd''' repo zypper rr < '''number of repo''' ''or'' '''name of repo''' ''or'' '''alias of repo'''> *add community repo: Packman zypper ar -f http://packman.inode.at/suse/openSUSE_12.1 packman In the end you should have the following repos: <pre> # zypper lr --uri # | Alias | Name | Enabled | Refresh | URI --+------------------------------------+------------------------------------+---------+---------+------------------------------------------------------------- 1 | Updates-for-openSUSE-12.1-12.1-1.4 | Updates for openSUSE 12.1 12.1-1.4 | Yes | Yes | http://download.opensuse.org/update/12.1/ 2 | packman | Packman repository (openSUSE_12.1) | Yes | No | http://packman.inode.at/suse/openSUSE_12.1 3 | repo-non-oss | openSUSE-12.1-Non-Oss | Yes | Yes | http://download.opensuse.org/distribution/12.1/repo/non-oss/ 4 | repo-oss | openSUSE-12.1-Oss | Yes | Yes | http://download.opensuse.org/distribution/12.1/repo/oss/ </pre> ==Kernel stuff== Install this stuff now, because sooner or later you will need them. And sometimes the install/compile of a kernel module will fail without these zypper in -y kernel-source linux-kernel-headers kernel-syms make gcc ==utils== zypper in -y mc findutils-locate nmap yakuake krusader chromium clementine vlc unetbootin p7zip krename ==For multimedia stuff & codecs:== # zypper in -y flash-player flashplayer-kde4 mplayer ffmpeg a52dec mencoder x264 faac w32codec-all lame kdemultimedia4-thumbnailers optional: # zypper in -y gstreamer-0_10-plugins-good xine-browser-plugin swfdec-browser-plugin gxine-browser-plugin gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-ugly mplayerplug-in libxine1-codecs k3b-codecs gstreamer-0_10-ffmpeg for windows movies in webbrowser: # zypper in gnome-mplayer gecko-mediaplayer =fonts= To install MS fonts so that LibreOffice documents looks closer to those on my colleagues' screen, execute the following (as root): zypper in fetchmsttfonts ==Language:== zypper in -y ispell-dutch myspell-dutch If you have installed from liveCD, localization may be missing: zypper in -y kde4-l10n-nl kde4-l10n-nl-data kde4-l10n-nl-doc ==firefox:== *install add-ons: adblock, xmarks *add 'new tab' button in buttonbar *configuration: **download location always ask, close when ready etc **start with blank page **do not remember history, suggest from bookmarks **search for text when I start typing **no check my spelling as I type **no check to see if FF is default browser *==>install silverlight plugin http://go-mono.com/moonlight-beta/<== maybe not *type about:config in addressbar and change: **network.dns.disableIPv6 -> true **create this one: content.notify.backoffcount -> 5 **also create nglayout.initialpaint.delay -> 0 **network.http.pipelining true **network.http.proxy.pipelining true **network.http.pipelining.maxrequests 8 ==KDE:== *edit /etc/sysconfig/windowmanager and change this option to 'no' KDE_USE_IPV6="no" (probably already is) *taskbar: **add system monitor CPU usage widget **digital clock: add day of week *add yast2 and configure desktop to quick start area (next to suse-icon) *configure desktop - personal settings: **region and language: region: dutch. add dutch to languages **advanced -> session manager: start KDE with empty session **autostart: yakuake konversation pidgin **desktop screensaver: random *desktop: add analogue clock widget *configure powermanagement *configure kwin *configure fonts ==Yast2:== *configure NTP settings 194.109.22.18 (XS4All time server) or choose from pool.ntp.org ==OOo== *User details *quickstarter ==Printer configuration== *cups printer 192.168.1.1 ++ALWAYS USE IP++ ==Power settings== ==network mounts== 4a89be5062088ceaa8995b9ffe257cb9c547ef8d 0 391 1465 1464 2012-03-16T13:19:40Z Root 1 wikitext text/x-wiki 32GB <pre> sda1 200MB ext3 /boot WeTabOS sda2 2GB swap sda3 12,5GB ext3 / WeTabOS sda4 ==== extended partition ======= sda6 200mb /boot plasma sda7 9GB / plasma sda5 7GB ext2 androidx86 / \ | LETOP 612337464a774d965af03e5302116977b75818b9 0 413 1468 1467 2012-03-24T17:30:38Z Root 1 /* Snelle koolhydraten */ wikitext text/x-wiki = Gezond ouder worden met eten uit de steentijd = Laatste update:&nbsp; 23 maart 2012 16:2info6 == GRONINGEN - Oervoeding uit de steentijd kan, vertaald naar de 21ste eeuw, een belangrijke bijdrage leveren aan gezond ouder worden. == Het menselijk DNA is in zekere zin afgestemd op het voedsel dat in de oudheid beschikbaar was. Dat bestond toen uit meer eiwitten en omega-3 vetzuren en minder koolhydraten en linolzuur. Dat stelt onderzoeker Remko Kuipers van het Universitair Medisch Centrum Groningen (UMCG) in een onderzoek waarop hij 26 maart aan de Rijksuniversiteit Groningen promoveert. Kuipers onderzocht waar onze voorouders leefden, maakte een reconstructie van hun voeding en onderzocht de voeding van traditioneel levende Oost-Afrikaanse volkeren in de huidige tijd. Daaruit blijkt volgens hem dat typisch westerse ziektes zoals hart- en vaatziektes en depressies verband houden met een tekort aan vetzuren, bouwstoffen die in de oudheid volop aanwezig waren in het voedsel. == Pijlsnel == ''Ons voedselpatroon is in 10.000 jaar pijlsnel veranderd. Maar onze genen niet, die zijn nog gebaseerd op de jager/verzamelaar in de steentijd'', zegt Kuipers. ''Evolutionair is dat niet verantwoord. Het leidt ertoe dat steeds meer mensen sneller ziek worden.'' Kuipers concludeert verder dat de oervoeding veel minder linolzuur bevatte dan tegenwoordig. Linolzuur zou volgende de heersende opvattingen een beschermende werking hebben op het ontstaan van hart- en vaatziektes. Volgens Kuipers klopt dat niet. Hij stelt dat recente studies juist laten zien dat de aanbevolen vervanging van verzadigde vetzuren door linolzuur in het Westen eerder tot een toename dan een afname van hart- en vaatziekten heeft geleid. == Snelle koolhydraten == Ook zogeheten snelle koolhydraten (suikers in frisdranken en snoep) als vervanging van verzadigd vet verhogen juist de kans op hart- en vaatziekten, meent Kuipers. Deze bevindingen komen volgens hem overeen met hoe onze oervoeding ooit was. Volgens Kuipers is dé oplossing om koolhydraten uit het voedsel te bannen. ''We zijn doorgeslagen in het gebruik van koolhydraten als rijst, brood, aardappelen en pasta. Ik zou dat allemaal willen weglaten en vervangen door groente en fruit, eventueel aangevuld met vis en vlees.'' (c) ANP 348a4a6ac5ee54df1afa337c1e3aeb04f5e90356 0 414 1470 2012-03-24T17:33:29Z Root 1 Created page with "[[Gezond ouder worden met eten uit de oertijd]]" wikitext text/x-wiki [[Gezond ouder worden met eten uit de oertijd]] 5daa5f67f1b9af47589fa125a6958b230c48866f 0 369 1471 1259 2012-04-09T14:05:49Z Root 1 wikitext text/x-wiki <pre>lap088:/home/pvdm # cat /etc/zypp/repos.d/* [packman] name=Packman enabled=1 autorefresh=1 baseurl=http://packman.inode.at/suse/openSUSE_12.1 type=rpm-md gpgcheck=1 gpgkey=http://packman.inode.at/suse/openSUSE_12.1/repodata/repomd.xml.key keeppackages=0 [pvdm-garmin] name=pvdm-garmin enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_12.1/ type=rpm-md [pvdm-kde48-extra] name=pvdm-kde48-extra enabled=1 autorefresh=1 baseurl=http://pvdm.xs4all.nl/kde48extra/ type=rpm-md keeppackages=0 [pvdm-kde48] name=pvdm-kde48 enabled=1 autorefresh=1 baseurl=http://pvdm.xs4all.nl/kde48/ type=rpm-md keeppackages=0 [pvdm-kernel] name=pvdm-kernel enabled=1 autorefresh=1 baseurl=http://pvdm.xs4all.nl/kernel/ type=rpm-md keeppackages=0 [pvdm-nntpgrab] name=pvdm-nntpgrab enabled=0 autorefresh=1 baseurl=http://www.openftd.org/releases/openSUSE_12.1 type=rpm-md keeppackages=0 [pvdm-smoothfonts] name=pvdm-smoothfonts enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/repositories/home:/muzlocker/openSUSE_12.1/ type=rpm-md keeppackages=0 [repo-non-oss] name=Non-Oss enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/distribution/12.1/repo/non-oss/ path=/ type=yast2 keeppackages=0 [repo-oss] name=Oss enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/distribution/12.1/repo/oss/ path=/ type=yast2 keeppackages=0 [Updates] name=PvdM Updates enabled=1 autorefresh=1 baseurl=http://pvdm.xs4all.nl/update/12.1/ path=/ type=rpm-md keeppackages=0 </pre> fb9361d64ed8ce51eac5f1c969eaf51e19ad0585 0 99 1472 591 2012-04-26T07:33:42Z Root 1 wikitext text/x-wiki *xine http://217.196.35.12/asx/radioveronica.asx *http://listen.soulradio.com/soulradio.pls *http://listen.soulradio.com/soulradio.m3u 68266e75992ed3114e148c35cf68da701bd68303 8 415 1478 1477 2012-04-27T07:34:35Z Root 1 javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ /* document.write('<script type="text/javascript" src=" + 'http://en.wikipedia.org/w/index.php?title=User:CaCycle/wikEd.js' + &action=raw&ctype=text/javascript"></' + 'script>'); */ 0506855880328e4a5239eb2963ab10d43a1c17a8 0 416 1480 2012-04-27T15:23:41Z Root 1 Created page with " gpsbabel -t -i garmin -f usb: -o gpx -F test.gpx" wikitext text/x-wiki gpsbabel -t -i garmin -f usb: -o gpx -F test.gpx ccbde834a17c5ec3bf87370cfb33e384086d51de 0 417 1483 1482 2012-04-30T07:03:01Z Root 1 wikitext text/x-wiki *http://www.bartberghmans.be/WandelenOostenrijk.htm **http://www.tripadvisor.nl/Tourism-g811455-Leutasch_Tirol_Austrian_Alps-Vacations.html c8e19bd7c02722144903ce74e6f855d10afd44cc 0 130 1484 784 2012-05-06T20:54:31Z Root 1 wikitext text/x-wiki *[[dvgrab]] *[[kdenlive]] *[[radeon]] d1aab1fccb033d61b086800b93bc569ac0d9e75c 0 418 1487 1486 2012-05-06T20:56:24Z Root 1 wikitext text/x-wiki - The Radeon hardware was tested with the following non-stock options: *disabling swap buffers wait from the xorg.conf (SwapbuffersWait), *enabling 2D color tiling (ColorTiling and ColorTiling2D in xorg.conf), *and enabling PCI Express 2.0 support (radeon.pcie_gen2=1 as a kernel command-line parameter). It is silly that these non-default options are still needed for the open-source driver that AMD officially supports, but that is how it stands right now. - With the Nouveau driver the main performance-boosting item at this point is forcing the graphics card manually into its highest performance level / clock state. The Nouveau driver continues to leave the graphics core / memory / shader clocks at whatever the video BIOS to sets them at when initializing, unlike the NVIDIA binary driver that dynamically changes the performance levels based upon GPU load and other factors. Therefore, with most modern NVIDIA hardware having multiple performance levels, to get the GPU at the correct frequencies for 3D use you need to manually force them to the higher state. Meanwhile you need to hope that the NVIDIA driver properly supports re-clocking for your GPU and that once re-clocked you don't experience any rendering corruption or stability problems. Re-clocking involves loading the Nouveau DRM driver with a special command-line parameter and writing the desired performance level to a sysfs node. This information is covered in detail in Nouveau Reclocking: Buggy, But Can Boost Performance. I long for the day when the Nouveau driver properly supports re-clocking across all modern NVIDIA GPUs and can be enabled by default to be done automatically. 87d668a836b9d6616d50745b08e60721605a225d 0 420 1533 1532 2012-05-19T07:13:21Z Root 1 wikitext text/x-wiki This article explains how I was able to get my Garmin Forerunner 305 working with linux, and upload my runs to the website of garmin connect. This is mainly a copy of the excellent article [http://braiden.org/?p=62 here]. And this article is just my summary of the steps needed to get the stuff working. 56fbfcac0650d4f0b55bcccd40f5d74d6f1ee0cd 0 421 1536 2012-05-20T13:33:17Z Root 1 Created page with "setup -> tv settings -> general : 4th page This way won't conflict with back to back recordings" wikitext text/x-wiki setup -> tv settings -> general : 4th page This way won't conflict with back to back recordings 08c1dcd82d12fc8ebb732866c37131cd06c9c96f 0 422 1538 2012-05-20T13:35:25Z Root 1 Created page with "capture card -> recorder options -> max recordings : 3 is a sensible setting" wikitext text/x-wiki capture card -> recorder options -> max recordings : 3 is a sensible setting 829f2a0e0a425a7e0ae5e1c0349aa6a62a6f1208 0 423 1543 2012-06-08T12:49:24Z Root 1 Created page with "=Netfilter= Elke Linux distributie gebruikt Netfilter (in de kernel) voor firewalling. De beheertool daarvoor is ''''iptables'''', via de commandline. Hoe werkt het? Er zijn ..." wikitext text/x-wiki =Netfilter= Elke Linux distributie gebruikt Netfilter (in de kernel) voor firewalling. De beheertool daarvoor is ''''iptables'''', via de commandline. Hoe werkt het? Er zijn drie soorten verkeer: INPUT, OUTPUT en FORWARD. Dit worden ook wel ''''chains'''' genoemd. * INPUT is alles op je interface binnenkomt *OUTPUT is alles wat je interface verlaat *FORWARD is als de computer als router is geconfigureerd, dus met meerdere netwerkkaarten Om te beginnen, moeten we de firewall service stoppen. Op openSUSE is dat rcSuSEfirewall2 stop =controle= Vervolgens beginnen we met een schone lei. Verwijder alle firewall regels iptables -F Controleer dit met iptables -L -v =dichtzetten= Hierna staat je firewall uit en is leeg, dus we gaan hem snel dichtzetten. We gebruiken hiervoor ''''policies''''. iptables -p INPUT DROP iptables -p OUTPUT DROP iptables -p FORWARD DROP -p betekent hier policy, INPUT is de chain waarop hij werkt, en de ''''target'''' is ''''drop''''. =targets= Er zijn de volgende targets: * DROP: alle pakketjes worden gedropt, er is geen terugmelding * REJECT: het pakketje wordt verworpen, er gaat wel een melding terug * ACCEPT: het pakketje wordt geaccepteerd * LOG: er wordt een melding in syslog geschreven over het binnenkomende pakketje Nu is de computer potdicht, en er is dus niet mee te werken met communicatie naar buiten. We gaan hem zo inrichten dat er communicatie naar buiten mogelijk is. =loopback goedzetten= Maar eerst moet er de loopback interface (lo) goed geconfigureerd worden. Hoewel niet strikt noodzakelijk, maar dit zorgt ervoor dat een hoop zaken goed verlopen. iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT -A betekent 'append', aan het eind. De volgorde van de regels is belangrijk! De eerste 'hit' wordt uitgevoerd en er wordt daarna niet meer verder gekeken. -i is de interface -j (jump) naar welke target Hierna kan er gepinged worden naar de loopbackinterface: <pre> PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.034 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.019 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.027 ms </pre> =uitgaand verkeer toestaan= We gaan nu alle uitgaande verkeer toestaan. iptables -A OUTPUT -o eth0 -j ACCEPT Dit zorgt voor uitgaande pakketjes, maar antwoorden hierop die binnenkomen, kunnen nog steeds niet de computer bereiken. iptables -A INPUT -m state - state=ESTABLISHED,RELATED -j ACCEPT creert een stateful filter. e02ac89953a65dec97d30b42bf80f4e50aa3f5c2 0 148 1547 1366 2012-07-26T12:03:33Z Root 1 wikitext text/x-wiki =Partities= OCZ Onyx Series SATA II 32 GB SSD <pre> 1. /boot 200MB 2. swap 1GB 3. Xbmc 8GB 4. ext. part. 5. XbmcFreak 6GB 6. OS 11.4 8GB / 7. OS 12.1 6GB / 8. (parted) print Model: ATA OCZ-ONYX (scsi) Disk /dev/sda: 32.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 206MB 204MB primary ext2 type=83 2 206MB 1283MB 1078MB primary linux-swap(v1) type=82 3 1283MB 9870MB 8587MB primary ext4 type=83 4 9871MB 32.0GB 22.1GB extended boot, lba, type=0f 5 9871MB 16.3GB 6439MB logical ext4 type=83 6 16.3GB 24.9GB 8587MB logical ext4 type=83 7 24.9GB 32.0GB 7105MB logical ext4 type=83 #fdisk -l Disk /dev/sda: 32.0 GB, 32017047552 bytes 255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000dc891 Device Boot Start End Blocks Id System /dev/sda1 2048 401407 199680 83 Linux /dev/sda2 401408 2506751 1052672 82 Linux swap / Solaris /dev/sda3 2506752 19277823 8385536 83 Linux /dev/sda4 * 19279870 62509055 21614593 f W95 Ext'd (LBA) /dev/sda5 19279872 31856639 6288384 83 Linux /dev/sda6 31858688 48629759 8385536 83 Linux /dev/sda7 48631808 62509055 6938624 83 Linux </pre> 1bd5b3af58377592076957daa20311d485106728 0 425 1551 2012-08-25T11:39:41Z Root 1 Created page with "To rearrange the channel list, use this shell script: <pre> #!/bin/sh # # a small shell script for automatic ordering of TV channels in MythTV # # BIG FAT WARNING: this scrip..." wikitext text/x-wiki To rearrange the channel list, use this shell script: <pre> #!/bin/sh # # a small shell script for automatic ordering of TV channels in MythTV # # BIG FAT WARNING: this script was tested only with MythTV v0.23. # Future versions of mythtv possibly use an incompatible database layout. # # The following workflow is recommended: # 1) backup the current channel settings: # ./channel_sort_mythtv.sh dump >mythtv_channels_dump.sql # 2) retrieve the current list of channel names # ./channel_sort_mythtv.sh get >channels.list # 3) sort the channels in 'channels.list' with your favourite text editor # 4) upload the new channel order (starting from channum=1): # ./channel_sort_mythtv.sh set <channel.list # # After another channel scan you can run this script again with the # 'merge' argument. It reads your current channel order from stdin # and appends all 'new' channels (taken from the database). # # # Copyright 2010 Lars Kruse <devel@sumpfralle.de> # # This script is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 2 of the License, or # (at your option) any later version. # # This script is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this script. If not, see <http://www.gnu.org/licenses/>. set -eu # you can override the mysql.txt location by providing it via an environment variable MYSQL_CONF_FILE=${MYSQL_CONF_FILE:-} # only used for "set" operation: # use this channel number for all channels, that are listed in stdin # set it to an empty string, if the channels, that are not listed, should remain untouched DEFAULT_CHANNEL=10000 # set DEBUG to a non-empty string to output the result sql statements instead of executing them # use something like "export DEBUG=true" before running this script to enable debug mode DEBUG=${DEBUG:-false} export DEBUG # read the mysql connection settings from the myth config # this exposes DBHostName, DBUserName, DBName and DBPassword for mysql_config in "$MYSQL_CONF_FILE" ~/.mythtv/mysql.txt /etc/mythtv/mysql.txt; do if test -n "$mysql_config" && test -r "$mysql_config"; then . "$mysql_config" break fi done # temporarily disable the "unset variable check" of bash set +u if test -z "$DBHostName" -o -z "$DBUserName" -o -z "$DBName" -o -z "$DBPassword"; then echo "Failed to read the mysql settings file of MythTV." >&2 echo "You can set the environement variable MYSQL_CONF_FILE to specify a custom location." >&2 fi set -u send_mysql_statement() { if test "$DEBUG" != "false"; then # only output the sql statements - don't execute them cat - else mysql -h "$DBHostName" -u "$DBUserName" --password="$DBPassword" --skip-column-names "$DBName" fi } show_syntax() { echo "Syntax: $(basename "$0") ACTION" echo "Possible actions:" echo " get - get all unsorted channel names from the database (to stdout)" echo " set - read the desired order of channels (by name) from stdin" echo " merge - output stdin and add all channel names (from the database)" echo " that were not listed before (to stdout)" echo " dump - dump the current state of the 'channel' table (as a backup)" echo " help - show this syntax description" echo "Hint: the 'get' operation does to same as 'merge' with empty stdin." } ACTION=invalid test $# -gt 0 && ACTION="$1" case "$ACTION" in get) # get distinct names and ignore empty lines echo "SELECT DISTINCT BINARY name FROM channel ORDER BY LPAD(channum, 3, 0) ASC;" \ | send_mysql_statement \ | grep -v "^$" ;; set) ( # reset all channel numbers to the default value if it is not empty test -n "$DEFAULT_CHANNEL" && echo "update channel set channum='$DEFAULT_CHANNEL';" current_num=1 cat - | grep -v "^$" | while read channel; do # escape single quotes channel=$(echo "$channel" | sed "s/'/\\\\'/g") echo "update channel set channum=$current_num where BINARY name='$channel';" current_num=$((current_num + 1)) done ) | send_mysql_statement ;; merge) input="$(cat -)" echo "$input" "$0" get | while read channel; do echo "$input" | grep -q "^$channel$" || echo "$channel"; done ;; dump) mysqldump -h "$DBHostName" -u "$DBUserName" --password="$DBPassword" "$DBName" channel ;; help|--help|invalid) if test "$ACTION" = "invalid"; then show_syntax >&2 exit 1 else show_syntax fi ;; esac exit 0 </pre> 2d899f2e8576aaa40015776947226076baaee395 0 105 1552 1550 2012-08-25T11:41:06Z Root 1 wikitext text/x-wiki *[[How to check the MythTV database]] *[[How to check the channel list]] *[[How to rearrange the channel list]] *[[Start recordings early and end late]] *[[simul rec]] *[[Linux - MythTV - Technotrend - DVB-C - Ziggo]] 283acd9a4450f7c2d414c05568cb376ef92448ff 0 419 1579 1578 2012-10-01T11:02:35Z Root 1 /* enabling the kernel head repository */ wikitext text/x-wiki It is possible to have the latest kernel in openSUSE. However, there are a few thing you must consider. These will be discussed below. We will be using the command line tool '''zypper''' to update to the latest kernel, because it is easier than YaST :D =stock kernels= OpenSUSE is installed (from DVD or wherever from) with a kernel called the 'stock' kernel. Sometimes this kernel is also referred to the '''GA kernel'''. This kernel remains the same for the whole time that that specific openSUSE version is supported, and is only updated with security issues and occasional bug fixes. This is called backporting. These updated stock-kernels appear in the ''update'' channel just as normal updates, so you should install them, just as other updates. This is a list of the latest openSUSE versions and their stock kernels: <pre> openSUSE version: stock-kernel 12.2 3.4.6-2.10 12.1 3.1.9 upgraded to 3.1.10 for security/bugfixes 11.4 2.6.37 </pre> =kernel versions= openSUSE has the option to run other 'flavours' of the kernel. These include: *'''kernel-default''' -> The standard kernel for both uniprocessor and multiprocessor systems. *'''kernel-desktop''' -> This kernel is optimized for the desktop. It is configured for lower latency and has many of the features that aren't usually used on desktop machines disabled. *'''kernel-pae''' -> this is a 32-bit only special kernel with support for 64GB memory. 64 bit kernels support this by default *'''kernel-vanilla''' -> The standard kernel - without any SUSE patches *'''kernel-xen''' -> The Linux kernel for Xen paravirtualization. This kernel can be used both as the domain0 ("xen0") and as an unprivileged ("xenU") kernel. Usually, for a desktop/laptop system, you run the ''default'' or the ''desktop'' flavour. =keeping older kernel versions as fallback= It is good practice, when you enable the ''kernel-head'' repo and thus recieve the latest and greatest kernel, to keep some previous kernel(s) at hand to use as a fallback scenario. These kernels will appear in your grub menu so you will be able to choose them when booting up your machine. Fortunately, '''zypper''' supports this with a few configuration options. It is possible for instance to instruct zypper to keep the stock kernel, the latest kernel, and the latest but one and to remove all others. That is cool, right? The magic is in the file <tt>/etc/zypp/zypp.conf</tt>. There are two options there: multiversion = provides:multiversion(kernel) multiversion.kernels = latest,oldest The first line enables the mutiple installation of kernels simultaniously. This is not possible by default, so this option is necessary. The second has several options: <pre>## Comma separated list of kernel packages to keep installed in parallel, if the ## above multiversion variable is set. Packages can be specified as ## 2.6.32.12-0.7 - Exact version to keep ## latest - Keep kernel with the highest version number ## latest-N - Keep kernel with the Nth highest version number ## running - Keep the running kernel ## oldest - Keep kernel with the lowest version number (the GA kernel) ## oldest+N - Keep kernel with the Nth lowest version number ## ## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set #multiversion.kernels = latest,oldest </pre> So, if you want to keep the stock kernel and the latest kernel, use: multiversion.kernels = latest,oldest If you want to keep the stock kernel, the latest and the kernel before that, use: multiversion.kernels = latest,oldest,latest-1 =enabling the kernel head repository= To receive the latest kernel, you must create an additional repo to download from. zypper ar -f http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ kernel-repo This command add a new repository (ar), enables refresh (-f), provides the URL, and a name (kernel-repo). This repository always contains the lastest development kernel, i.e. 3.4.0-rc6-1-desktop. Do not expect to find older versions there, it is always the latest and only the latest build! This repo is the same for '''all''' openSUSE version, =updating from the new repo= To actually download and install the new kernel, you must do a special update. This is called a distribution-upgrade. Don't worry, this won't update your entire installation! We will instruct zypper to only use updated packages from the kernel-repo we just created. A normal 'zypper up' won't replace packages from a different repo then the one it was originally installed from. Issue the command: zypper dup -r kernel-repo This tells zypper to do a dist-upgrade from the kernel-repo, so only your new kernel files will be installed alongside the old ones, if you have properly configured the zypp.conf file. =check check double check= After you have completed these instructions, you can check which kernels you have installed: rpm -qa | grep kernel The output of that command on my system at time of this writing: <pre> #rpm -qa | grep kernel | sort kernel-default-devel-3.4.rc3-3.1.x86_64 kernel-default-devel-3.4.rc6-1.1.x86_64 kernel-desktop-3.4.rc3-3.1.x86_64 kernel-desktop-3.4.rc6-1.1.x86_64 kernel-desktop-devel-3.4.rc3-3.1.x86_64 kernel-desktop-devel-3.4.rc6-1.1.x86_64 kernel-devel-3.4.rc3-3.1.noarch kernel-devel-3.4.rc6-1.1.noarch kernel-source-3.4.rc3-3.1.noarch kernel-source-3.4.rc6-1.1.noarch kernel-syms-3.4.rc3-3.1.x86_64 kernel-syms-3.4.rc6-1.1.x86_64 kernel-xen-devel-3.4.rc3-3.1.x86_64 kernel-xen-devel-3.4.rc6-1.1.x86_64 </pre> As you can see, I have 2 kernels installed at the moment: '''3.4.rc3''' and '''3.4.rc6'''. (The rest of the packages are necessary for other purposes, like Virtualbox.) e4fe0f018f0b72151624c32c34edde5cea517c4a 0 430 1581 2012-10-02T14:31:46Z Root 1 Created page with "*[[specs lapx]] *[[partitions lapx]] *[[grub lapx]] *[[repos lapx]]" wikitext text/x-wiki *[[specs lapx]] *[[partitions lapx]] *[[grub lapx]] *[[repos lapx]] e58547ef2f766615564c03d6950067b6a36cea3b 0 432 1585 2012-10-11T15:26:09Z Root 1 Created page with " mogrify -colorspace RGB -format jpg -quality 100 img00*.pcd[5]" wikitext text/x-wiki mogrify -colorspace RGB -format jpg -quality 100 img00*.pcd[5] b6403f227dd79582f41948304f377d1165535ad6 0 433 1587 2012-10-27T07:52:28Z Root 1 Created page with "= How to Get a List of Permissions of MySQL Users = MySQL has advanced database access system. A database user can have access to the whole database, separate tables, or to se..." wikitext text/x-wiki = How to Get a List of Permissions of MySQL Users = MySQL has advanced database access system. A database user can have access to the whole database, separate tables, or to separate columns of tables. Also there is a restriction for actions a user may perform with records. MySQL server uses several tables in a special database to organize such a complicated database access structure. The access policy is based on the values available in these tables. The database that MySQL server uses to store internal data about users is called&nbsp;mysql&nbsp;by default. There are tables for storing information about users’ accounts in this database: * '''''user'''''&nbsp;contains a list of all users of the MySQL server and their permissions to access the database; * '''''db'''''&nbsp;contains a list of databases with a matching list of database users and their privileges for executing operations; * '''''tables_priv'''''&nbsp;contains a list of database tables (views) that a user has access to; * '''''columns_priv'''''&nbsp;contains a list of columns from the database tables (views) a user has access to; * '''''procs_priv'''''&nbsp;contains a list of database procedures (functions) a user has access to.<br/> To get the list of users’ privileges concerning data access, the following queries may be executed: '''* the list of global privileges: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>mu.host `Host`, <tt>&nbsp;</tt>mu.user `User`, <tt>&nbsp;</tt>REPLACE(RTRIM(CONCAT( <tt>&nbsp;</tt>IF(mu.Select_priv = 'Y', 'Select ', ''), <tt>&nbsp;</tt>IF(mu.Insert_priv = 'Y', 'Insert ', ''), <tt>&nbsp;</tt>IF(mu.Update_priv = 'Y', 'Update ', ''), <tt>&nbsp;</tt>IF(mu.Delete_priv = 'Y', 'Delete ', ''), <tt>&nbsp;</tt>IF(mu.Create_priv = 'Y', 'Create ', ''), <tt>&nbsp;</tt>IF(mu.Drop_priv = 'Y', 'Drop ', ''), <tt>&nbsp;</tt>IF(mu.Reload_priv = 'Y', 'Reload ', ''), <tt>&nbsp;</tt>IF(mu.Shutdown_priv = 'Y', 'Shutdown ', ''), <tt>&nbsp;</tt>IF(mu.Process_priv = 'Y', 'Process ', ''), <tt>&nbsp;</tt>IF(mu.File_priv = 'Y', 'File ', ''), <tt>&nbsp;</tt>IF(mu.Grant_priv = 'Y', 'Grant ', ''), <tt>&nbsp;</tt>IF(mu.References_priv = 'Y', 'References ', ''), <tt>&nbsp;</tt>IF(mu.Index_priv = 'Y', 'Index ', ''), <tt>&nbsp;</tt>IF(mu.Alter_priv = 'Y', 'Alter ', ''), <tt>&nbsp;</tt>IF(mu.Show_db_priv = 'Y', 'Show_db ', ''), <tt>&nbsp;</tt>IF(mu.Super_priv = 'Y', 'Super ', ''), <tt>&nbsp;</tt>IF(mu.Create_tmp_table_priv = 'Y', 'Create_tmp_table ', ''), <tt>&nbsp;</tt>IF(mu.Lock_tables_priv = 'Y', 'Lock_tables ', ''), <tt>&nbsp;</tt>IF(mu.Execute_priv = 'Y', 'Execute ', ''), <tt>&nbsp;</tt>IF(mu.Repl_slave_priv = 'Y', 'Repl_slave ', ''), <tt>&nbsp;</tt>IF(mu.Repl_client_priv = 'Y', 'Repl_client ', ''), <tt>&nbsp;</tt>IF(mu.Create_view_priv = 'Y', 'Create_view ', ''), <tt>&nbsp;</tt>IF(mu.Show_view_priv = 'Y', 'Show_view ', ''), <tt>&nbsp;</tt>IF(mu.Create_routine_priv = 'Y', 'Create_routine ', ''), <tt>&nbsp;</tt>IF(mu.Alter_routine_priv = 'Y', 'Alter_routine ', ''), <tt>&nbsp;</tt>IF(mu.Create_user_priv = 'Y', 'Create_user ', ''), <tt>&nbsp;</tt>IF(mu.Event_priv = 'Y', 'Event ', ''), <tt>&nbsp;</tt>IF(mu.Trigger_priv = 'Y', 'Trigger ', '') <tt>&nbsp;</tt>)), ' ', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.user mu '''ORDER''' '''BY''' <tt>&nbsp;</tt>mu.Host, <tt>&nbsp;</tt>mu.User |} '''* the list of privileges for a database: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>md.host `Host`, <tt>&nbsp;</tt>md.user `User`, <tt>&nbsp;</tt>md.db `'''Database'''`, <tt>&nbsp;</tt>REPLACE(RTRIM(CONCAT( <tt>&nbsp;</tt>IF(md.Select_priv = 'Y', 'Select ', ''), <tt>&nbsp;</tt>IF(md.Insert_priv = 'Y', 'Insert ', ''), <tt>&nbsp;</tt>IF(md.Update_priv = 'Y', 'Update ', ''), <tt>&nbsp;</tt>IF(md.Delete_priv = 'Y', 'Delete ', ''), <tt>&nbsp;</tt>IF(md.Create_priv = 'Y', 'Create ', ''), <tt>&nbsp;</tt>IF(md.Drop_priv = 'Y', 'Drop ', ''), <tt>&nbsp;</tt>IF(md.Grant_priv = 'Y', 'Grant ', ''), <tt>&nbsp;</tt>IF(md.References_priv = 'Y', 'References ', ''), <tt>&nbsp;</tt>IF(md.Index_priv = 'Y', 'Index ', ''), <tt>&nbsp;</tt>IF(md.Alter_priv = 'Y', 'Alter ', ''), <tt>&nbsp;</tt>IF(md.Create_tmp_table_priv = 'Y', 'Create_tmp_table ', ''), <tt>&nbsp;</tt>IF(md.Lock_tables_priv = 'Y', 'Lock_tables ', ''), <tt>&nbsp;</tt>IF(md.Create_view_priv = 'Y', 'Create_view ', ''), <tt>&nbsp;</tt>IF(md.Show_view_priv = 'Y', 'Show_view ', ''), <tt>&nbsp;</tt>IF(md.Create_routine_priv = 'Y', 'Create_routine ', ''), <tt>&nbsp;</tt>IF(md.Alter_routine_priv = 'Y', 'Alter_routine ', ''), <tt>&nbsp;</tt>IF(md.Execute_priv = 'Y', 'Execute ', ''), <tt>&nbsp;</tt>IF(md.Event_priv = 'Y', 'Event ', ''), <tt>&nbsp;</tt>IF(md.Trigger_priv = 'Y', 'Trigger ', '') <tt>&nbsp;</tt>)), ' ', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.db md '''ORDER''' '''BY''' <tt>&nbsp;</tt>md.Host, <tt>&nbsp;</tt>md.User, <tt>&nbsp;</tt>md.Db |} '''* the list of privileges for tables: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>mt.host `Host`, <tt>&nbsp;</tt>mt.user `User`, <tt>&nbsp;</tt>CONCAT(mt.Db, '.', mt.Table_name) `Tables`, <tt>&nbsp;</tt>REPLACE(mt.Table_priv, ',', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.tables_priv mt '''WHERE''' <tt>&nbsp;</tt>mt.Table_name IN <tt>&nbsp;</tt>('''SELECT''' <tt>&nbsp;</tt>'''DISTINCT''' <tt>&nbsp;&nbsp;&nbsp;</tt>t.table_name `tables` <tt>&nbsp;</tt>'''FROM''' <tt>&nbsp;&nbsp;&nbsp;</tt>information_schema.tables '''AS''' t <tt>&nbsp;</tt>'''WHERE''' <tt>&nbsp;&nbsp;&nbsp;</tt>t.table_type IN <tt>&nbsp;&nbsp;&nbsp;</tt>('BASE TABLE', 'SYSTEM VIEW', 'TEMPORARY', '') OR <tt>&nbsp;&nbsp;&nbsp;</tt><nowiki>t.table_type <> </nowiki>'VIEW' AND <tt>&nbsp;&nbsp;&nbsp;</tt>t.create_options '''IS''' NOT NULL <tt>&nbsp;</tt>) '''ORDER''' '''BY''' <tt>&nbsp;</tt>mt.Host, <tt>&nbsp;</tt>mt.User, <tt>&nbsp;</tt>mt.Db, <tt>&nbsp;</tt>mt.Table_name; |} '''* the list of privileges for views: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>mv.host `Host`, <tt>&nbsp;</tt>mv.user `User`, <tt>&nbsp;</tt>CONCAT(mv.Db, '.', mv.Table_name) `Views`, <tt>&nbsp;</tt>REPLACE(mv.Table_priv, ',', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.tables_priv mv '''WHERE''' <tt>&nbsp;</tt>mv.Table_name IN <tt>&nbsp;</tt>('''SELECT''' <tt>&nbsp;</tt>'''DISTINCT''' <tt>&nbsp;&nbsp;&nbsp;</tt>v.table_name `views` <tt>&nbsp;</tt>'''FROM''' <tt>&nbsp;&nbsp;&nbsp;</tt>information_schema.views '''AS''' v <tt>&nbsp;</tt>) '''ORDER''' '''BY''' <tt>&nbsp;</tt>mv.Host, <tt>&nbsp;</tt>mv.User, <tt>&nbsp;</tt>mv.Db, <tt>&nbsp;</tt>mv.Table_name; |} '''* the list of privileges for table columns: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;&nbsp;</tt>mtc.host `Host`, <tt>&nbsp;&nbsp;</tt>mtc.user `User`, <tt>&nbsp;&nbsp;</tt>CONCAT(mtc.Db, '.', mtc.Table_name, '.', mtc.Column_name) `Tables Columns`, <tt>&nbsp;&nbsp;</tt>REPLACE(mtc.Column_priv, ',', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;&nbsp;</tt>mysql.columns_priv mtc '''WHERE''' <tt>&nbsp;&nbsp;</tt>mtc.Table_name IN <tt>&nbsp;&nbsp;</tt>('''SELECT''' <tt>&nbsp;&nbsp;</tt>'''DISTINCT''' <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt>t.table_name `tables` <tt>&nbsp;&nbsp;</tt>'''FROM''' <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt>information_schema.tables '''AS''' t <tt>&nbsp;&nbsp;</tt>'''WHERE''' <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt>t.table_type IN <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt>('BASE TABLE', 'SYSTEM VIEW', 'TEMPORARY', '') OR <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt><nowiki>t.table_type <> </nowiki>'VIEW' AND <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt>t.create_options '''IS''' NOT NULL <tt>&nbsp;&nbsp;</tt>) '''ORDER''' '''BY''' <tt>&nbsp;&nbsp;</tt>mtc.Host, <tt>&nbsp;&nbsp;</tt>mtc.User, <tt>&nbsp;&nbsp;</tt>mtc.Db, <tt>&nbsp;&nbsp;</tt>mtc.Table_name, <tt>&nbsp;&nbsp;</tt>mtc.Column_name; |} '''* the list of privileges for view columns: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>mvc.host `Host`, <tt>&nbsp;</tt>mvc.user `User`, <tt>&nbsp;</tt>CONCAT(mvc.Db, '.', mvc.Table_name, '.', mvc.Column_name) `Views Columns`, <tt>&nbsp;</tt>REPLACE(mvc.Column_priv, ',', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.columns_priv mvc '''WHERE''' <tt>&nbsp;</tt>mvc.Table_name IN <tt>&nbsp;</tt>('''SELECT''' <tt>&nbsp;</tt>'''DISTINCT''' <tt>&nbsp;&nbsp;&nbsp;</tt>v.table_name `views` <tt>&nbsp;</tt>'''FROM''' <tt>&nbsp;&nbsp;&nbsp;</tt>information_schema.views '''AS''' v <tt>&nbsp;</tt>) '''ORDER''' '''BY''' <tt>&nbsp;</tt>mvc.Host, <tt>&nbsp;</tt>mvc.User, <tt>&nbsp;</tt>mvc.Db, <tt>&nbsp;</tt>mvc.Table_name, <tt>&nbsp;</tt>mvc.Column_name; |} '''* the list of privileges for procedures: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>mp.host `Host`, <tt>&nbsp;</tt>mp.user `User`, <tt>&nbsp;</tt>CONCAT(mp.Db, '.', mp.Routine_name) `Procedures`, <tt>&nbsp;</tt>REPLACE(mp.Proc_priv, ',', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.procs_priv mp '''WHERE''' <tt>&nbsp;</tt>mp.Routine_type = 'PROCEDURE' '''ORDER''' '''BY''' <tt>&nbsp;</tt>mp.Host, <tt>&nbsp;</tt>mp.User, <tt>&nbsp;</tt>mp.Db, <tt>&nbsp;</tt>mp.Routine_name; |} '''* the list of privileges for functions: ''' {| style="border-spacing:0;" | style="border:none;padding:0cm;"| '''SELECT''' <tt>&nbsp;</tt>mf.host `Host`, <tt>&nbsp;</tt>mf.user `User`, <tt>&nbsp;</tt>CONCAT(mf.Db, '.', mf.Routine_name) `Procedures`, <tt>&nbsp;</tt>REPLACE(mf.Proc_priv, ',', ', ') '''AS''' `'''Privileges'''` '''FROM''' <tt>&nbsp;</tt>mysql.procs_priv mf '''WHERE''' <tt>&nbsp;</tt>mf.Routine_type = 'FUNCTION' '''ORDER''' '''BY''' <tt>&nbsp;</tt>mf.Host, <tt>&nbsp;</tt>mf.User, <tt>&nbsp;</tt>mf.Db, <tt>&nbsp;</tt>mf.Routine_name; |} 560d3b585e1e09afe497f99b1f2df92d7d79bdaa 0 154 1590 1589 2012-11-06T12:25:23Z Root 1 wikitext text/x-wiki ⊙_ʘ >.< ☺ ☹ – frowning face ☺ – smiley face <pre> [11:15] <SUSEhelp> Commands in admin: gc, gcs, join, memory and raw. [11:15] <SUSEhelp> Commands in alias: addhelp, alias, list, lock, remove, removehelp, setcorealias, showalias and unlock. [11:15] <SUSEhelp> Commands in blist: add, addfromfile, count, deletelist, deletematching, get and list. [11:15] <SUSEhelp> Commands in calc: calc. [11:15] <SUSEhelp> Plugin flood has no commands. [11:15] <SUSEhelp> Commands in googleweather: weather. [11:15] <SUSEhelp> Commands in help: blockhelp, commands, help, longhelp, plugins, summary and syntax. [11:15] <SUSEhelp> Commands in miscmsg: 8ball, bugreport, ct, date, discordiandate, exchange, featurerequest, flipacoin, random, serveruptime, time, uptime and week. [11:15] <SUSEhelp> Commands in nickserv: check and clearcache. [11:15] <SUSEhelp> Commands in options: get, getgeneral, help, list, listgeneral, set and setgeneral. [11:15] <SUSEhelp> Commands in plugin: detach, info, list, load, reload, setcore, source and unsetcore. [11:15] <SUSEhelp> Commands in quote: add, count, create, get, info, karmamod, last, remove and summary. [11:15] <SUSEhelp> Commands in security: addgroup, addtogroup, adduser, beginlink, deluser, findpermission, grant, link, removefromgroup and revoke. [11:15] <SUSEhelp> Commands in see: bodyclock, firstseen, freshers, midday and pattern. [11:15] <SUSEhelp> Commands in seen: seen. [11:15] <SUSEhelp> Commands in susefactoids: delete, factinfo, forget, getchannellanguage, link, remember, search, setchannellanguage, unlink and whatis. [11:15] <SUSEhelp> Commands in talk: describe, me, msg, privme, privmsg, reply, say and shout. [11:15] <SUSEhelp> Commands in tell: get and send. [11:15] <SUSEhelp> Commands in timedevents: at, in and last. [11:15] <SUSEhelp> Commands in timezone: timein and whenis. [11:15] <SUSEhelp> Commands in topic: diff and get. [11:15] <SUSEhelp> Commands in vote: abstainall, activevotes, call, info and vote. </pre> !alsa ALSA (Advanced Linux Sound Architecture) provides your Linux sound drivers. For basic openSUSE sound concepts, check out: http://en.opensuse.org/Sound-concepts !sound Basic openSUSE audio troubleshooting guide is at http://en.opensuse.org/SDB:Audio_troubleshooting !pulseaudio PulseAudio is a sound server intended as replacement for !ESD. Some info on openSUSE pulseaudio: http://en.opensuse.org/Pulseaudio Disable: http://en.opensuse.org/Disabling_PulseAudio_HowTo For detailed information on pulseaudio, please go here: http://pulseaudio.org/wiki/AboutPulseAudio. See "perfect" setup http://www.pulseaudio.org/wiki/PerfectSetup !anybody Please do not ask if anyone uses, knows, is good with, can help you with or is a guru/expert of <someprogram>. Instead, ask your real question. (If the real question _was_ "does anyone use <someprogram>?" --- Also: !sicco !research !smartquestion !question !ask Don't ask to ask, just ask :) (and try to explain exactly what the problem is, which openSUSE version you're using, on what architecture, etc...) --- !sicco [20:52] <SUSEhelp> Please ask sicco questions: questions that are Specific, Informative, Concise, Complete, and On-topic. !ati To install the proprietary ATI drivers see http://en.opensuse.org/SDB:ATI_drivers - Note: ATi dropped support for the non-HD series in their proprietary fglrx driver, DO NOT install this driver if your card is legacy. !best There are often no "best" things, such as filesystems, window managers or Linux distributions. You pick the one you find most suitable/appealing and do not rely on people's "recommendation" as an excuse. !beta If you want a stable machine that is easy to setup and relatively problem free, DO NOT use a beta OS! If you are VERY comfortable with Linux/SuSE and wish to help the developers by submitting bug reports, don't mind instability, and understand that many features may not work correctly or at all, then go for it. For support post on the opensuse-factory mailing list !chat Offtopic chat (i.e., not related to openSUSE support) is in #opensuse-chat !codecs There are several multimedia formats that cannot be included on the openSUSE CDs/DVD because they are proprietary, patented, restricted formats. Some of these include MP3, MPEG-4, playing of encrypted DVDs, etc. Information on how to install proprietary codec support on openSUSE, please visit; http://opensuse-community.org/Restricted_formats !compiz !counter openSUSE 11.4 countdown: http://countdown.opensuse.org/large - also see http://en.opensuse.org/Portal:11.4 for a list of some of the features !dup You can do a live distribution upgrade with openSUSE. Valid upgradeable releases are from 10.3 on. You can find the how-to here: http://wiki.opensuse.org/SDB:System_upgrade !dvd There are several multimedia formats that cannot be included on the openSUSE CDs/DVD because they are proprietary, patented, restricted formats. Some of these include MP3, MPEG-4, playing of encrypted DVDs, etc. Information on how to install proprietary codec support on openSUSE, please visit; http://opensuse-community.org/Restricted_formats !enter Please don't use the <Enter> key as punctuation! !everygreen The Evergreen project aims to provide Long Time Support for certain openSUSE versions, see http://en.opensuse.org/openSUSE:Evergreen !hclwlan To check the compatibility of wlan cards take a look at: Network Adapters (Wireless) Hardware Compatibility List (HCL) http://en.opensuse.org/HCL:Network_%28Wireless%29 . (also http://linux-wless.passys.nl/) !hello !hi Hello! Welcome to the English openSUSE support channel. Don't be shy. PLEASE don't ask if anyone can help; share which openSUSE version and state detailed questions. We hope you find support needed here. Enjoy your visit. Type: "/msg SUSEhelp !helpme" (no quotes) here for more info how to use our time-saving self-help bot! !helpme Welcome to an openSUSE irc support channel. To get help from me you can ask for keywords (factoids) in PRIVATE please with /msg SUSEhelp factoid. To search for keywords try /msg SUSEhelp search keyword. !kotd kotd; Kernel Of The Day (and mirrors) can be found at http://download.opensuse.org/repositories/Kernel:/HEAD/ (need support? see factoid !beta) !lifetime !liveusb For instructions on how to create an installable, persistent, openSUSE Live USB, see: http://en.opensuse.org/SDB:Live_USB_stick !new2irc If you are new to IRC take a look at Communicate/IRCforNewbies please at http://en.opensuse.org/Communicate/IRCforNewbies !ntfs !obs !packages Search for packages on the openSUSE Build Service here: http://software.opensuse.org/search - You can browse Packman packages here: http://packman.links2linux.org/packages !packman Packman is the most popular third-party repository available for openSUSE and contains software that cannot be included in the distribution for legal reasons. Instructions on how to add Packman to your openSUSE installation can be found at http://opensuse-community.org/Repositories !paste Please don't paste more than 3 lines in the channel; instead, use one of http://paste.opensuse.org/ , http://pastebin.com/ or http://pastie.org/ -- for pics, use http://img.susepaste.org/ , http://picpaste.com/ or http://min.us/ !patience Patience is a virtue. Double true in community open source distro support channels like #suse where UNpaid volunteers do their best to help. Please respect their time with your patience. !pmthebot Please use the SUSEhelp self help bot in private queries when not introducing new users in main channel to factoids & help us keep the channel cleaner by typing ' /msg SUSEhelp factoid' OR '/msg SUSEhelp search some keyword'. THANKS & know SUSEhelp bot is here for all ;-) !redirector TarDisk: download.opensuse.org is a redirector. It redirects to mirrors near you. Sometimes it will redirect you to bad mirror and sometimes the redirector itself is down !repeat please do not repeat yourself !repos See http://opensuse-community.org/Repositories for how to add the basic repositories. !runlevel for info on runlevels go here: http://en.wikipedia.org/wiki/Runlevel and http://en.opensuse.org/System_Services_(runlevel) !sax2 SaX2 is dropped from 11.3 onwards and there's no xorg.conf by default. Auto-detection should "just work" in most cases. If you must configure X use xrandr, krandrtray, gnome display settings, nvidia-settings, ATI catalyst control center etc. depending on your card/driver, or manually edit /etc/X11/xorg.conf.d/ - or as last resort, manually create /etc/X11/xorg.conf !skype !smartquestion !software !studio !support General technical support is in #suse (/join #suse), please ask over there !tumbleweed The Tumbleweed project aims to provide a rolling updates version of openSUSE containing the latest stable versions instead of relying on rigid periodic release cycles. See http://en.opensuse.org/Tumbleweed for details. !usb !usb-install !vendorchange !vlc !wifi !wine !zypper zypper is the easy to use commandline interface to the YaST (openSUSE PM pattern) package management. See http://en.opensuse.org/Portal:Zypper e73e50251344fe8b7d2916ddcbcc974156d489a8 0 435 1599 1598 2012-11-25T10:39:31Z Root 1 wikitext text/x-wiki http://www.surrounddiscography.com/dvdaudio/dvdaudio.htm dvd-a <pre> - James Brown & The Soul G's - Live at Chastain Park - Beach Boys - Pet Sounds - Led Zeppelin - How The West Was Won - Sting - Sacred Love - Alan Parsons - On Air * Queen - The Game - The Who - Tommy - Grandmaster Flash, Melle Mel & The Furious Five - Greatest Hits * Rush - A Farewell to Kings (Included in the Sector 2 Box Set) * Rush - Fly By Night (Included in the Sector 1 Box Set) * Rush - Moving Pictures (DVD-Audio sold seperatly and also included the Sector 3 Box Set) - Melle Mel & The Furious 5 - Greatest Hits of Grandmaster Flash - Yes - Magnification - Yes - Fragile - Simple Minds - New Gold Dream - Simple Minds - Once Upon A Time - Alanis Morissette - Under Rug Swept - The Eagles - Hotel California - Metallica- Metallica - Steely Dan - Everything Must Go - Jean-Michel Jarre - Teo & Tea 44dbcc2ba4f532717fa0976ded40aa46532a09af 0 135 1600 721 2012-11-28T09:18:32Z Root 1 wikitext text/x-wiki *5a !!! [[File:Model-5a.jpg]] *model3 *Model 3 8-In, 4-out 2 Monitor (8x4x2) portable mixer. *1983...M-30 *M-35　(8x4x2)an 8-in, 4-out, 8 monitor *M-35EX expansion to 28 inputs. *M-50 12 input, 8-buss　2 aux *M106 (6x4x4) *M208 !! (1985 8x4x2) *M216 (16x4x4) *M308 (8x4x8) 83e1f7eb535882a63e4211acd5b25b270a314156 0 429 1622 1621 2013-04-17T08:55:58Z Pvdm 2 /* Groeispurten */ wikitext text/x-wiki =Buxus= ==Hoe Buxus knippen ?== Het knippen dient vooral vaak te gebeuren. De meeste tuinliefhebbers beperken het aantal knipbeurten tot 2 keer in het jaar. Wil je echt mooie buxus in je tuin dan moet je minimaal 4 keer in het seizoen gaan knippen. Vooral voor grotere exemplaren is dit van belang. De plant wordt hierdoor veel voller en sterker. Bovendien geven ze een veel mooier beeld. Een probleem bij te snel gegroeide en te weinig geknipte buxusbollen is dat ze bij regen-en sneeuwval uitzakken waardoor er een gat in de bol onstaat. Ook als je begint met een kleine maat plant ga je hem dus al regelmatig snoeien voor de stevigheid. Je behoeft de plant alleen niet geheel terug te knippen tot op de oude snede. Anders kan je nooit groter komen. ==Wanneer Buxus knippen ?== Knip de eerste keer al vrij vroeg in het seizoen, zo begin mei. Hou daarna de groei in de gaten. De volgende knipbeurten doe je telkens als de nieuwe scheutjes zo’n 4 à 5 cm lang zijn. In de periode van felle zonneschijn (jul.-aug.) is het belangrijk niet geheel terug te knippen tot op de oude snede. Maar iets hoger. Dit voorkomt verbranding(bruinverkleuring). Snoei de buxus altijd op een bewolkte dag, want door de zon kunnen de blaadjes verbranden. Wil je toch in de zon snoeien, besproei hem dan eerst met water en leg er als je klaar bent een fleecedoek overheen. De eerstvolgende knipbeurt na deze periode kan je dan weer terug naar de oorspronkelijke kniphoogte. Na half september is het verstandig de buxus niet meer te knippen anders heeft de plant niet meer de tijd om voldoende af te harden voor de winter. ==Groeispurten== De buxus heeft twee groeispurten. Eén in het voorjaar en één in het najaar. ''In februari of maart is het tijd voor de eerste snoeibeurt. Dit is voor de eerste uitloop van de plant. Door te snoeien voor het uitlopen, heeft de plant nog kans om gedurende het voorjaar verder uit te lopen. Snoei je de buxus te laat, dan groeit deze niet meer verder.'' <-- enige referentie voor zo vroeg snoeien, dus niet doen. De tweede groeispurt is middenin de zomer. De langste dag van het jaar (21 juni) is goed aan te houden voor een tweede snoeibeurt. Zo kan de buxus in de nazomer nog een keer uitlopen. Om de hele winter een strakke buxushaag te hebben kun je deze ook nog een keer snoeien in oktober/november. Snoei je te vroeg, bijvoorbeeld in augustus of september, en krijgen we een warm najaar? Dan is de buxus gevoeliger voor de vorst. Uit voorzorg kun je dit dus beter niet doen. Snoeitips *Sproei vóór het snoeien de buxus nat, dat knipt beter *Gebruik uitsluitend een scherpe snoei- of heggenschaar *Om de bladeren niet te laten verkleuren moet je niet snoeien in de volle zon *Begin eerst met de zijkanten en daarna met de bovenkant *Span een touwtje om overal dezelfde hoogte te snoeien *Houd genoeg ruimte aan de onderkant vrij voor voldoende zonlicht =Lechuza= ==Aglaonema Silverbay== '''standplaats''' Heel donker, lichter mag ook maar absoluut geen direct zonlicht. '''water en voeding''' In de lichte maanden, mei t/m september mag je elke twee weken een beetje plantenvoeding meegeven. Tussen twee gietbeurten mag de grond best een beetje opdrogen. '''temperatuur''' Jouw Aglaonema heeft het het beste naar zijn zin wanneer de dagtemperatuur zo tussen de 20 en 25 graden Celsius schommelt. Let er op dat de nachttemperatuur niet te laag wordt. 16-18 graden is prima, maar niet lager! ==Calathea Ruf. Mirosha== '''standplaats''' De Calathea wordt ook wel schaduwplant genoemd, omdat deze plant van nature in het dichtbegroeide tropische regenwoud van Zuid-Amerika groeit. De Mirosha mag dan ook niet in het directe zonlicht staan, het liefst een halfschaduw plekje en een temperatuur tussen de 16 en 27 graden. '''water en voeding''' Tijdens de groei de grond vochtig houden met lauw water. Regelmatig water geven en eenmaal in de 14 dagen bijmesten, dan zult u lang plezier van deze mooie kamerplant hebben. Let u vooral eens op de specifieke eigenschap van de Calathea. Tegen de avond sluiten de bladeren zich, dit geeft een ruisend geluid. De volgende ochtend staat hij weer met zijn bladeren te pronken. ==Goudpalm== Naam:Chrysalidocarpus lutescens Areca lutescens Nederlandse naam: goudpalm, arekapalm Familie: Palmae Herkomst: Madagaskar '''Standplaats:''' Geen volle zon of direct zonlicht maar wel veel licht. Een warme, lichte plaats maar geen felle middagzon. Ook ’s nachts mag de temperatuur niet onder 15°C zakken. Ideale temp.: 18-24°C Temperatuurschommelingen vermijden. In de zomer eventueel buiten op een beschutte plaats. '''Water:''' Houd de potgrond gelijkmatig vochtig, vooral in de groeiperiode. De potgrond best gelijkmatig vochtig houden.en zeker niet laten uitdrogen. Regelmatig nevelen of dompelen om de luchtvochtigheid te bevorderen. Gebruik water op kamertemperatuur. '''Algemeen:'''De mooie opwaartse beweging van deze sierlijke kamerpalm straalt opgewekte energie aan haar omgeving af. Chrysalidocarpus kent geen centrale stam, de bladstengels komen allemaal rechtstreeks uit de grond. Het blad is opvallend smal, glanzend donkergroen en de stengels zijn geelachtig, wat de plant in haar thuisland Madagaskar de bijnaam Goudpalm heeft opgeleverd. Met een gelijkmatige kamertemperatuur en een altijd iets vochtige kluit kan ook een kleine versie zo geestdriftig groeien dat er al snel sprake is van een binnenboom '''Tip:''' Regelmatig benevelen bij een kamertemperatuur van 18°C. Gebruik gedistilleerd water of regenwater. •Deze palm uit Madagascar is de meest gebruikte van de palmsoorten. Vooral geliefd omwille van zijn tropische uiterlijk. Verpot de plant in het voorjaar om de 2 à 3 jaar. 077da1270892d2059651e351385e3accc8dbf806 0 439 1625 1624 2013-05-19T20:04:57Z Pvdm 2 wikitext text/x-wiki De dB Auteur: Hans Beekhuyzen Als je je met audio en video bezighoudt, kan je niet om de decibel oftewel dB heen. Toch zorgt de dB nog wel eens voor verwarring, dus is het tijd voor een uitleg.. In de begintijd van de telefoon was in Amerika Bell Company aan het onderzoeken hoe groot (telefoon-)lijnverliezen waren. Men ontdekte dat als je lijnverliezen uitdrukte in vermogensverlies, dus in watts, er weinig relatie was met de gehoormatige ervaring van het verlies. Dus heeft men een eenheid ontwikkeld die dat wel had: de Bel. Eén Bel toename werd gedefinieerd als een verdubbeling van waargenomen luidheid. Daarvoor bleek een tienvoudige vermogen voor nodig te zijn. In de begintijd was dat best een probleem, want het hele systeem werkte zonder versterking. Als je meer signaal wilde, dan moest je gewoon harder schreeuwen. En om een zo hoog mogelijk rendement te krijgen, werden de impedanties van microfoon (zender) en luidspreker (ontvanger) op elkaar aangepast om zoveel mogelijk vermogen door de leiding te krijgen. Dit concept van gelijke impedanties aan zend- en ontvangstkant - de zogenaamde stroomaanpassing - werd later overgenomen door omroepen; het zogenaamde 600 ohm systeem. En ook thuis was er vaak sprake van impedantieaanpassing. Want omdat buizenversterkers relatief hoogohmig uit gaan in vergelijking met een luidspreker, wordt een uitgangstransformator gebruikt die ook weer voor een optimale impedantieaanpassing aan beide kanten zorgt. Bel luiden Maar terug naar de dB; zoals gezegd spreek je van 1 Bel als het geluid twee keer zo hard klinkt en daarvoor is tien keer zoveel vermogen nodig. Even een staatje: 0 Bel = 1 W
 - referentieniveau 1 Bel = 10 W
 - twee keer zo hard 2 Bel = 100 W - drie keer zou hard 3 Bel = 1000 W - vier keer zo hard Het leuke is dat het aantal nullen in het vermogen het getal in Bel aangeeft. Wiskundigen noemen dat logaritme en je schrijf het zo: 0 Bel = 1 x 1 = 1 W (referentieniveau) 1 Bel = 1 x 10¹ = 10 W (klinkt +1 keer harder) 2 Bel = 1 x 10² = 100 W (klinkt +2 keer harder) 3 Bel = 1 x 10³ = 1000 W (klinkt +3 keer harder) Het logaritme van een getal is de exponent (het kleine cijfertje) van een basisgetal (bij dB’s altijd 10). Maar maak je er niet te sappel om; als je het concept begrijpt dan kan elke zakjapanner het rekenwerk doen. De formule is: Om de formule uit te rekenen deel je eerst de ene vermogenswaarde door de andere, drukt op de log knop van de rekenmachine. Reken het verschil tussen 2 W en 15 W maar eens uit: Deel 15 door 2 (of andersom), je krijgt 7,5 als uitkomst. Druk op de log knop en controleer de uitkomst: 0,87506..... oftewel 0,875 Bel. Al snel bleek dat de Bel een veel te grove maat was, dus ging men werken met tienden van een Bel: de decibel. Dat is ook meteen ongeveer het kleinste niveauverschil dat we met ons gehoor kunnen waarnemen bij ongewijzigde klankbalans. Dat betekent dus dat 10 dB twee keer zo hard klinkt en dat daar 10 keer zoveel vermogen voor nodig is. De formule is natuurlijk gelijk aan die van de Bel, alleen wordt nu de uitkomst met 10 vermenigvuldigd: Spanning en sensatie Hiervoor had ik het er al over dat er zo min mogelijk vermogen verloren gaat als er een optimale impedantieaanpassing is. Maar tegenwoordig gebruiken we zelden nog impedantieaanpassingen in analoge audio. Het is nu niet meer nodig om het vermogen van de bron zo effectief mogelijk over te brengen omdat het veel eenvoudiger is op de juiste plekken versterking toe te passen. Het enige wat we willen is een zo goed mogelijke representatie van het audiosignaal en dat kan ook met spanning. Zolang je zorgt dat de ingangsimpedantie van het ontvangende apparaat minimaal tien keer zo groot is als de uitgangsimpedantie van het zendende apparaat, is de stroom redelijk beperkt en geeft de spanning een prima ‘plaatje' van het signaal. Maar dat heeft wel gevolgen voor het rekenen in dB's want vermogen is de spanning in het kwadraat gedeeld door de impedantie: Als we nu de dB formule aanpassen voor spanning, krijgen we: De eerste formule is zoals we hem kennen voor vermogen. Aangezien we spanning willen berekenen, vervangen we het symbool voor vermogen (P) door de formule en zien we de tweede stap. In de derde stap hebben we in de deling de weerstand verwijderd omdat we aannemen dat die in beide gevallen gelijk is (dat mag omdat bijvoorbeeld 600 ohm gedeeld door 600 Ohm 1 is). In de vierde stap hebben we het kwadraat van beide U's buiten de haakjes gehaald en in de vijfde stap verhuist die tweede macht naar het begin van de formule en omdat we daar aan de andere kant van de logaritmeberekening zijn (dus in het exponent van 10 rekenen), mogen we de 2 met de 10 vermenigvuldigen. Als we het dus over stroom hebben, dan is de formule: terwijl bij spanning de volgende formule geldt: Ok, we kunnen nu dB's berekenen dus iedereen weet wat 12 dB is? Nee dus. Want de dB is een verhoudingsmaat, zoals uit de deling in de formule ook valt af te leiden. Je kunt alleen maar verschillen uitrekenen en geen absolute waarden. Maar +4 dB was toch 1,22 V, het pro lijnniveau in de studio? Nee, want er is niet aangegeven ten opzichte van welke andere spanning gerekend is. Gelukkig is dat ook gestandaardiseerd, waardoor we de dB als quasi-absolute waarde kunnen gebruiken. dBm Als we teruggaan naar de begintijd van de omroep, dan zien we stroomaanpassingen op transformatorgebalanceerde 600 Ohm lijnen. Men bepaalde dat 1 milliwatt over 600 Ohm als algemene referentie werd genomen en noemde dat de dBm. De dBm is dus een vermogensverhouding met als referentie 1 mW over 600 Ohm. Nu wordt vermogen gemeten door een spanningsval over een bekende weerstand te meten en terug te rekenen naar vermogen met de eerder genoemde formule. In het geval van 0 dBm meet je 0,775 V spanningsval over een 600 Ohm weerstand. Wederom vereenvoudigd geeft dit de volgende formule: Maar omdat in de audiotechniek nog maar zelden gebruik wordt gemaakt van een stroomaanpassing, wordt de dBm nog maar zelden gebruikt. Maar het heeft wel zijn gevolgen gehad voor de toekomst, want in die situatie moesten volgens de NAB (North American Broacaster) VU-meters worden afgeregeld op +4 VU om te compenseren voor de traagheid van de VU -meter. +4 VU Boven 0 dBm komt overeenkomt met een spanningsval van 1,22 V over 600 Ohm. En daar is die 1,22 V weer! dBu Maar men bleef wel die 0,775 V als 0 dB referentie houden, ook in spanningsaanpassingen. Vooral in de tijd dat beide manieren naast elkaar werden gebruikt, was dat natuurlijk ook het handigst. Maar om aan te geven dat het nu alleen om spanning ging, werd de dBu (met de kleine u van spanning) uitgevonden. Dit is dus wel een spanningsverhouding en wordt dus uitgerekend met de formule: dBV Ondertussen ontstond er een logischer norm die 1V aanhoudt als referentie, de dBV, waarbij de grote V natuurlijk staat voor Volt. Ook hier hebben we het weer over een spanningsverhouding, dus geldt als formule: dBFS Met de komst van digitale apparatuur kwam er behoefte aan een digitale variant. Daarbij werd uitgegaan van het maximaal te registreren signaal, dus waarbij alle bits 1 zijn. Voor een 16-bits systeem ziet dat er als volgt uit: Je kunt het natuurlijk de binaire waarde omzetten in een decimale en je rekenwerk doen. Er zullen echter niet zoveel mensen zijn die zo werken, dus is het gebruikelijk de op het betreffende apparaat de voor 0 dBFS benodigde of afgegeven spanning als referentie te nemen. Veel cd-spelers geven 2V af bij 0 dBFS. Dus als je met zo'n cd-speler zonder signaal een spanning van 0,00004 V meet, dan heb je een signaal/ruisafstand van -93,97 dBFS. Reken het maar na. Nu kun je dus elke verhouding met dB's uitrekenen. Als je dit jaar € 60.000 hebt verdiend en vorig jaar € 56.400, hoeveel dB heb je dan meer verdiend. Wel dat hangt af of het om vermogen of spanning gaat! Een beetje een flauw grapje, maar het is een feit dat alles zich laat vertalen in verhoudingen en als die logaritmisch weergegeven meer zeggen dan lineair, dan is de dB een prima maat. Zo kun je uitrekenen wat de verschillen in signaal/ruisverhouding zijn tussen de diverse analoge bandrecorderkoppen. Amateurrecorders als van Revox en Teac gebruik(t)en bij tweespoorskoppen spoorbreedten van 2 mm terwijl Amerikaanse recorders als die van Ampex sporen van 2,4 mm breedte gebruikten. Dat scheelt meteen 1,6 dB aan signaal/ruisafstand. Europese recorders als van Studer en Telefunken konden uitgerust worden met zogenaamde vlinderkoppen en die schreven sporen van 2,7 mm hetgeen een signaal/ruisafstandsverbetering geeft van 2,6 dB ten opzichte van de amateurrecorder en 1 dB ten opzichte van Amerikaanse professionele recorders. dB SPL Ook geluidsniveau's kunnen met dB's gemeten worden en dat gebeurt ook. De bekendste is de dB SPL, decibel sound pressure level. Het referentieniveau is hier natuurlijk geluidsdruk en wel 0,0002 microbar en omdat het om een niveau gaat, gebruiken we de formule die ook voor spanning wordt gebruikt (je zou kunnen zeggen dat je het over membraanspanning hebt). Rest mij af te sluiten met een leuk voorbeeld over de misverstanden die de dB kan veroorzaken: enkele jaren geleden stond een stukje in een krant waarin een horeca-uitbater uit het Oosten des Lands was bekeurd voor het overtreden van de hinderwet met 12 dB. Volledig overtuigd van de onzin hiervan zij hij tegen de reporter: "Het was maar 12 dB te hard. Ik heb het opgezocht en 12 dB komt overeen met het geluid van een vallende speld." Hij vond dat hij dus maar het geluid van een vallende speld te hard had gedraaid. Ga daar maar eens tegenin. 2d7bf8288df8ab4eb141a96578ddca9a71bf928a 0 441 1633 2013-06-13T12:09:00Z Pvdm 2 Pvdm moved page [[Installing spotify on openSUSE 12.2]] to [[Installing spotify on openSUSE 12.3]] wikitext text/x-wiki #REDIRECT [[Installing spotify on openSUSE 12.3]] 7ede23371b60de8f3a02641be814f0dd1f95b357 0 428 1637 1636 2013-06-13T12:33:27Z Pvdm 2 wikitext text/x-wiki This guide shows you how to install spotify client on openSUSE 12.3 As there is no native openSUSE rpm, we will have to make one ourselves. The big advantage of this method is, that we will always have the latest version, because when a new version is released, we can bake a new rpm ourselves and don't have to wait on others. Here are the steps: 1. browse to http://repository.spotify.com/pool/non-free/s/spotify/ and download the appropriate 32- or 64 bit version. 2. install the rpm package 'alien' to convert .deb to .rpm's. This can be found in the opensuse repos, to be exact here: http://software.opensuse.org/package/alien 3. use alien to convert: #alien -r spotify-clientxxxxx.deb spotify-client-0.8.4.103.g9cb177b.260-2.x86_64.rpm generated 4. then, install the rpm: #zypper in spotify-client*.rpm you will get a libcrypto dependency error, but you can ignore that, choose 2: Solution 2: break spotify-client-0.9.0.133.gd18ed58.259-2.x86_64 by ignoring some of its dependencies 5. typ the following: ln -s /usr/lib64/libnss3.so /usr/lib64/libnss3.so.1d ln -s /usr/lib64/libnssutil3.so /usr/lib64/libnssutil3.so.1d ln -s /usr/lib64/libsmime3.so /usr/lib64/libsmime3.so.1d ln -s libplc4.so /usr/lib64/libplc4.so.0d ln -s libnspr4.so /usr/lib64/libnspr4.so.0d 6. that should do it. Have fun! cdf980cbb0cc8108c738513dad7274032d8d3d46 0 442 1644 2013-09-12T16:33:49Z Pvdm 2 Pvdm moved page [[Quad]] to [[Audio]] wikitext text/x-wiki #REDIRECT [[Audio]] 933b565304c332c4d7a58e0c5f359dd4c94353bc 0 444 1658 2013-11-07T11:26:00Z Pvdm 2 Created page with "*[[Amplifier JVC MCA-V7]]" wikitext text/x-wiki *[[Amplifier JVC MCA-V7]] ec1d1e11d6a9f6cdd1892d94db8e66d9b35d0918 6 446 1661 2013-11-07T11:32:57Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 445 1667 1666 2013-11-07T11:39:25Z Pvdm 2 wikitext text/x-wiki [[file:JVC_MCA_V7E.jpg|800px|right]] Around early 1970 (japanses translation) Commentary 4ch Amplifier equipped with a Sound Field Composer. I am equipped with a Sound Field Composer circuit where you can enjoy the atmosphere of 4ch in 2ch source. By a device to reproduce the pseudo 4ch, is output from the speakers of another reverberation only component that is included in the 2ch source, this circuit is aimed to reproduce the sense of reality. It uses a 2ch-4ch complementary circuit by BTL Type of actuation in the MCA-V7, to drive each speaker in the SEPP circuit four sets 4ch playback, I get a high-powered by BTL connection 2ch time. I have adopted a quasi-complementary ITL · OTL circuit to circuit configuration. In addition, with the aim of noise reduction by adopting a low-noise silicon transistor. Equalizer circuit has become a two-stage, and is stopping the transistor noise by using a PNP transistor in the first stage. 4ch and two inputs, it is equipped with the 4ch recording and playback terminal. It is equipped with an pre-out main-in terminal of 4ch, it can be used independently of the main amplifier and preamplifier. {| style="border-spacing:0;" | style="border:none;padding:0.049cm;"| {| style="border-spacing:0;" | style="border-top:0.05pt double #808080;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Model | style="border:0.05pt double #808080;padding:0.049cm;"| 4ch Amplifier |- | colspan="2" style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| <nowiki><Power amplifier section></nowiki> |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Circuit system | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| SEPP-OTL circuit, BTL switchable |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Music Power | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 45W +45 W (8Ω) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Effective output | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 12.5W × 4 (8ohms)&nbsp;28W +28 W (8ohms) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Harmonic distortion | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 0.08% (12.5W) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Intermodulation distortion | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 0.2% (12.5W) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Power Band Width | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 30Hz ~ 50kHz-3dB |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Frequency characteristic | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 20Hz ~ 100kHz ± 0.5dB |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| SN ratio | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 90dB or more |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Input sensitivity / impedance | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 0.6V/50kΩ |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Load impedance | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 8Ω ~ 16Ω |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Damping factor | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 50 (8Ω) |- | colspan="2" style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| <nowiki><Preamplifier></nowiki> |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Input sensitivity / impedance | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Phono: 3MV/50keiomega&nbsp;Tuner, Aux, Tape play, DIN: 50MV/100keiomega |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Phono maximum permissible input | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 100mV |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Tone control | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 4ch tone control, NF type&nbsp;Bass: ± 10 dB (100 Hz)&nbsp;Treble: ± 10 dB (10 kHz) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Output Impedance | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Pre out: 0.5V (nominal), 5V (maximum) / 1.2 kW&nbsp;Rec out: 36MV/4.7Keiomega&nbsp;DIN: 36MV/80keiomega |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Frequency characteristic | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Phono: RIAA ± 0.5 within&nbsp;20Hz ~ 40kHz +0-1.5dB: Aux |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Harmonic distortion | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 0.1% (1kHz, 2.5V) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Intermodulation distortion (60Hz: 70kHz = 4:1) | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 0.2% (2.5V) |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| SN ratio (IHF) | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Phono: 80dB&nbsp;Aux: 85dB |- | colspan="2" style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| <nowiki><More></nowiki> |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Input terminal | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Phono, Tuner, Aux, Tape play,&nbsp;4CH Aux, 4CH Disc, Main in |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Output terminal | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Pre out, Rec out, SP out |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| DIN terminal | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 1 system |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Attached circuit | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Tape monitor&nbsp;Sound Field Composer |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| The semiconductor used | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Transistor: 45 pieces&nbsp;Diode: 24 |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Power outlets | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| Power switch interlock: Dual&nbsp;power switch unsynchronized: 1 system |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Power | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| AC100V, 50Hz/60Hz |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| External dimensions | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 138 × depth 296mm height width 420 × |- | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:none;padding:0.049cm;"| Weight | style="border-top:none;border-bottom:0.05pt double #808080;border-left:0.05pt double #808080;border-right:0.05pt double #808080;padding:0.049cm;"| 10kg |} |} f1398101f4af97e8a317af831460061d2cb28c49 0 447 1675 1674 2013-11-28T13:23:46Z Pvdm 2 /* Optimize Tables using Mysqlcheck */ wikitext text/x-wiki =Check a Specific Table in a Database= If your application gives an error message saying that a specific table is corrupted, execute the mysqlcheck command to check that one table. The following example checks employee table in thegeekstuff database. # mysqlcheck -c thegeekstuff employee -u root -p Enter password: thegeekstuff.employee OK =Check All Tables in a Database= To check all the tables in a particular database, don’t specify the table name. Just specify the database name. The following example checks all the tables in the alfresco database. <pre> # mysqlcheck -c alfresco -u root -p Enter password: alfresco.JBPM_ACTION OK alfresco.JBPM_BYTEARRAY OK alfresco.JBPM_BYTEBLOCK OK alfresco.JBPM_COMMENT OK alfresco.JBPM_DECISIONCONDITIONS OK alfresco.JBPM_DELEGATION OK alfresco.JBPM_EVENT OK ..</pre> =Check All Tables and All Databases= To check all the tables and all the databases use the “–all-databases” along with -c option as shown below. <pre> # mysqlcheck -c -u root -p --all-databases Enter password: thegeekstuff.employee OK alfresco.JBPM_ACTION OK alfresco.JBPM_BYTEARRAY OK alfresco.JBPM_BYTEBLOCK OK .. .. mysql.help_category error : Table upgrade required. Please do "REPAIR TABLE `help_category`" or dump/reload to fix it! mysql.help_keyword error : Table upgrade required. Please do "REPAIR TABLE `help_keyword`" or dump/reload to fix it! ..</pre> If you want to check all tables of few databases, specify the database names using “–databases”. The following example checks all the tables in thegeekstuff and alfresco database. # mysqlcheck -c -u root -p --databases thegeekstuff alfresco Enter password: thegeekstuff.employee OK alfresco.JBPM_ACTION OK alfresco.JBPM_BYTEARRAY OK alfresco.JBPM_BYTEBLOCK OK .. =Analyze Tables using Mysqlcheck= The following analyzes employee table that is located in thegeekstuff database. # mysqlcheck -a thegeekstuff employee -u root -p Enter password: thegeekstuff.employee Table is already up to date Internally mysqlcheck command uses “ANALYZE TABLE” command. While mysqlcheck is executing the analyze command the table is locked and available for other process only in the read mode. =Optimize Tables using Mysqlcheck= The following optimizes employee table that is located in thegeekstuff database. # mysqlcheck -o thegeekstuff employee -u root -p Enter password: thegeekstuff.employee OK Internally mysqlcheck command uses “OPTIMIZE TABLE” command. When you delete lot of rows from a table, optimizing it helps to get the unused space and defragment the data file. This might improve performance on huge tables that has gone through several updates. =Repair Tables using Mysqlcheck= The following repairs employee table that is located in thegeekstuff database. # mysqlcheck -r thegeekstuff employee -u root -p Enter password: thegeekstuff.employee OK Internally mysqlcheck command uses “REPAIR TABLE” command. This will repair and fix a corrupted MyISAM and archive tables. =Combine Check, Optimize, and Repair Tables= Instead of checking and repairing separately. You can combine check, optimize and repair functionality together using “–auto-repair” as shown below. The following checks, optimizes and repairs all the corrupted table in thegeekstuff database. # mysqlcheck -u root -p --auto-repair -c -o thegeekstuff You an also check, optimize and repair all the tables across all your databases using the following command. # mysqlcheck -u root -p --auto-repair -c -o --all-databases If you want to know what the command is doing while it is checking, add the –debug-info as shown below. This is helpful while you are checking a huge table. <pre># mysqlcheck --debug-info -u root -p --auto-repair -c -o thegeekstuff employee Enter password: thegeekstuff.employee Table is already up to date User time 0.00, System time 0.00 Maximum resident set size 0, Integral resident set size 0 Non-physical pagefaults 344, Physical pagefaults 0, Swaps 0 Blocks in 0 out 0, Messages in 0 out 0, Signals 0 Voluntary context switches 12, Involuntary context switches 9 </pre> =Additional Useful Mysqlcheck Options= The following are some of the key options that you can use along with mysqlcheck. <pre> -A, –all-databases Consider all the databases -a, –analyze Analyze tables -1, –all-in-1 Use one query per database with tables listed in a comma separated way –auto-repair Repair the table automatically it if is corrupted -c, –check Check table errors -C, –check-only-changed Check tables that are changed since last check -g, –check-upgrade Check for version dependent changes in the tables -B, –databases Check more than one databases -F, –fast Check tables that are not closed properly –fix-db-names Fix DB names –fix-table-names Fix table names -f, –force Continue even when there is an error -e, –extended Perform extended check on a table. This will take a long time to execute. -m, –medium-check Faster than extended check option, but does most checks -o, –optimize Optimize tables -q, –quick Faster than medium check option -r, –repair Fix the table corruption </pre> 0ad74de856244f41f1df52e779bcea9c52f9ffbb 0 49 1676 363 2013-12-13T09:52:05Z Pvdm 2 wikitext text/x-wiki * [[kmail]] ==KDE4 has some new apps:== * Dragon - MM player * Kscd - CD player * Ksystemlog - Handy system log viewer, also realtime! View syslog, X-server log, kernel & others * Dolphin - Filemanager. Check it out, awesome * Marble - Geo prog * Ksysguard - Processmonitor. Cool -> also displays output from progs NOT started from terminal!! * Libksane - scan library ==Other things to try:== * kid3 - Kid3 easily tags multiple MP3, OGG/Vorbis, FLAC, MPC, MP4/AAC, MP2, Speex, TrueAudio and WAV. It supports ID3v1.1, ID3v2.3, ID3.2.4. This Package is available from the KDE:Community repository in the openSUSE Build Service. * http://vavai.net/2008/10/28/making-a-local-copy-of-opensuse-repository-mirror-server/ * [[Fix suspend to RAM on a HP8530p EliteBook on OpenSUSE 11.2]] * [[clear recently used documents permanently in KDE4]] aabe0e3af0def34caa063658778d6319a1078e81 0 449 1681 2013-12-13T12:31:51Z Pvdm 2 Created page with "*FF cache *chromium cache *.thumbnails *spotify localstorecache *.wine */var/tmp/kdecache-pvdm" wikitext text/x-wiki *FF cache *chromium cache *.thumbnails *spotify localstorecache *.wine */var/tmp/kdecache-pvdm 341ba63f1c1a7737412b2bc7734e66f2663370f2 0 448 1682 1679 2013-12-13T16:15:29Z Pvdm 2 /* Transfer mail and settings to another computer (or another user account on the same machine) */ wikitext text/x-wiki =Transfer mail and settings to another computer (or another user account on the same machine)= Solution: The messages are typically in ~/.kde/share/apps/kmail/. For very old installations of KMail, the messages can also be in ~/Mail. Note that KMail uses hidden sub-directories inside that directory, so you need to make sure to copy hidden directories as well. For settings you will need to copy the following files: <pre> ~/.kde/share/config/kmailrc, ~/.kde/share/config/mailtransports, (since KDE 4.0) ~/.kde/share/config/emaildefaults and ~/.kde/share/config/emailidentities .</pre> Your address book is usually stored in ~/.kde/share/apps/kabc/. Calendar data is in ~/.kde/share/apps/korganizer Be aware that some distributions use ~/.kde4 instead of ~/.kde/ for their KDE configuration data. Look at the output of the command kde4-config --localprefix if in doubt. From version 4.4 you may have some Akonadi-controlled entries that also need to be kept. Add to the above list - <pre> Everything under ~/.local/share/ Everything under ~/.config/akonadi/. ~/.kde/share/config/nepomukserverrc Everything under ~/.kde/share/apps/nepomuk/ (KAddressBook stores contact groups in Nepomuk.) </pre> If you plan to use an USB stick as transport medium for your data, be sure to format to a linux FileSystem. 33bb576fa68d242ccac3d4d5fa7ab8bb2bb1526e 0 452 1693 1692 2014-01-07T07:33:39Z Pvdm 2 wikitext text/x-wiki Fonts: #9 #9 #8 #8 #9 #8 #9 #9 3,4 & 6 5b7ee1b731ec148db00e668eeeabb628c711ab76 0 453 1697 1696 2014-01-07T18:03:53Z Pvdm 2 wikitext text/x-wiki Ik heb er nu een paar schoongemaakt in de knostie met een zelfgemaakt mengsel bestaande uit: Water uit de supermarkt, H10 van de fotograaf en Ajax allesreiniger. Had geen alcohol in huis dus denk probeer het eens zonder. Plaat schoon en zo goed als alle tikken en narigheid is weg. Geen stof aan de naald. Ga het maar eens een poosje zonder de alcohol doen. Dit gaat vooralsnog ook prima.Op 1 liter water 5ml H10 en en een paar druppels Ajax voor het ontvetten. Gaat het ook lekker van ruiken ;) Wat zit er dan voor rotzooi in regenwater? Ik gebruik het al meer dan 35 jaar zonder probleem. Een scheut gedenatureerde alcohol erbij doet de verdamping (drogen) versnellen. Maar wie platen nat speelt wil dat niet. Ben deze week maar eens begonnen met het reinigen van mijn oudste platen. Met een eigen brouwsel (1 deel 97% alcohol, 2 delen demi-water, en een druppel afwasmiddel op een halve liter) in een plantenspuit vinyl besproeien en schoonmaken met een microvezeldoekje. Droog deppen met keukenpapier. Naast de eigen Knosti vloeistof heb ik ook de reinigingsvloeistof van QS audio gebruikt. Ook prima, ik heb geen voorkeur voor één van de twee. QS laat geen pluisje aan de naald achter na de eerste keer afspelen, maar daar had ik sowieso geen problemen mee. Voor mij is het meer een kwestie van beschikbaarheid. Je schijnt de vloeistof ook heel goed zelf te kunnen aanmaken, van gedestilleerd water, isopropylalcohol en een drupje afwasmiddel, maar de juiste verhouding weet ik zo gauw niet. Ik heb me daar nog niet aan gewaagd. Inmiddels heb ik mijn hele collectie LP's (circa 300) zo behandeld. Mijn huidig recept is 1 teiltje met lauwwarm water, 2 theelepels Dreft Platinum en 1 eetlepel glansspoelmiddel. Als wasdoekje gebruik ik een zijdeachtige brillenschoonmaakdoek. Aleen een richting die de richting van de groven volgt en van binnen naar buiten werken. Naspoelen onder koud stromend water, even uit laten druipen en drogen met een hele zachte, niet-pluizende katoenen doek en klaar is kees. In gebieden met hard water zou ik aqua destillata aaraden. Een goed alternatief is het condenswater uit je wasdroger opvangen en dat filteren. Dan heb je (ook) bijna puur water zonder zouten die een neerslag n je groeven zouden kunnen geven. I have a Knosti antistat and I think it is the best thing since sliced bread - though the problems with their fluid i entirely agree, i had exactly the same problems :evil: After much experimentation i now use a 50/50 mix of (99 percent pure) Isoppropyl alchohol and de-ionised water in the Knosti, very slowly turn the record in only one direction 2 or 3 times without stopping, the results are fantastic, no crackles I've stopped using isopropanol in my cleaning solution, now it's just pure water and 20mls of a detergent from the lab at work (sorry don't know the name of it) it looks like PhotoFlo but not as strong. After a round or 7 each way in the trough I then rinse under the tap (thanx CL) with the spindle still attached. Then its another 3 complete rotations each way in the trough with a pure water and 2mls detergent solution and then a dry in the rack. I leave it as long as necessary to dry. The detergent in the final round is a wetting agent to stop beading. The more rotations in each direction the better the clean I have found, especially for second hand records. Once in a while I find a record needs a second clean this sometimes works and is definitely good for your mental condition if it works. :D 03c0ca26e1ddbdff4287ac1f0aea1eb9ef22e654 0 454 1699 2014-01-28T15:51:45Z Pvdm 2 Created page with "=dbx= No, Dolby A was developed in the 1960s for studios and Dolby B near the end of the decade as I understand it. A lot of people didn't see the need for it at first but it ..." wikitext text/x-wiki =dbx= No, Dolby A was developed in the 1960s for studios and Dolby B near the end of the decade as I understand it. A lot of people didn't see the need for it at first but it took off eventually and when introduced in cassette decks it made a difference with mostly lower grade ferrics as high end until Chrome tapes were introduced. Signal to noise figures then were in the realm of 40-55 dB so with good tape and B NR you could easily top 60 in a quality deck. This is actually good because it matched well with the phonograph stages of the day. When quieter sources and better circuits came about it became apparent that more was needed. This is likely how dbx got it's place in the market. dbx is short for David Brownfield(?) eXpander or similar. As I recall it was introduced around 1971? The concept is brilliant and seems frightfully simple, whether it was then or not. With voltage control amplifiers (VCA) the level can be logarithmically reduced by 50% and expanded to the original 1:1, technically pushing the perceived noise floor far below that acheived by Dolby (30 dB is a good figure, can be more). When a version is applied to records the results (dbx disc) can be closer to what we'd expect from a CD. Static, deposits and wear would be the lone drawbacks, no longer a real noise factor. With a good quality of vinyl and pressing the sound can be quite nice! I've heard that the Teac reel to reel decks with dbx actually use type II but don't quote me. I have a model 155 4-channel type I and two, soon to be three NX-40 units. Type II isn't so inferior that it won't suffice for reel recordings and type III and onward have been introduced in recent times in professional equipment. Other offerings from the company have included limiters, single-ended expanders, routing switchers like the 200 amd 400 series and a large range of professional equipment. The current company is a part of Harman International and is mainly a professional audio equipment provider. 6434c7ea01a1784fbdd164fa0bcfb1c8137afde2 0 436 1700 1607 2014-01-28T15:52:09Z Pvdm 2 /* dbx */ wikitext text/x-wiki As an A-3440 enthusiast, I'm glad to hear you were able to get the issue resolved, thanks to Sam, he's the man! I'm just curious if you can check the serial # on the back of yours, which indicates the manufacturing date (the digits on the right side of the s/n). I believe the A-3440 was introduced in '78 (not sure if was the beginning of the year, or more toward later), along with its matching 2A mixer. (My older brother bought one new back in '79, when I was a teenager). The Tascam 34 came out in '82-'83, but I find it interesting that the A-3440 didnt seem to be discontinued, and was still being made at the same time as the 34. Does anyone recall what the $ price difference between them was?, just curious. I have a collection of Teac/Tascam literature, and it appears that the A-3440 and 2A were still around as late as 1984. Anyone know if the 40-4 made it that far as well? I was also curious if there were any revisions made to the A-3440 during its production run. Is an '83 A-3440 exactly identical to a '78 model, or are any circuit boards and components, etc different? I know the Model 2 (2A) mixer had a few slight changes- the knob colors and fader controls, and also had the raised meter bridge with faux-wood panels... Just a few lil' details I find interesting, if anyone else might also relate. Tapetech,Yes .the two micro swt's that the tension arm makes contact with.The one that engages the pinch roller was bad.Teac p/n is 51300010. Hi BeatleFred, The items in the A3440 that need attention are pots, capstan motor and belt as well as the Pinch Roller Linkage for grease issues. I have had a few electronics failures in the past but I would say that the electronic failures will come more often due to caps than in the past. The changing of a lot of Electrolytic caps by a good technician can not be that hard as the cards pull out the bottom and can very easily be done on the bench. Much easier than an X1000R or A3340S. They should be changed as they are going to be drying up. After 30 years of sitting and power being applied scarcely they can not be that long lasting plus this is not a large investment in parts. Who knows, in 2 or 3 years the current Electrolytic capacitor might be all gone due to lack of manufacturing and then everyone will be scurrying around trying to find some and end up with the Chinese caps that won't be a plus to use. Nobody sees this better than I on the front line. Get them done, date the board as to when and move on using a well operating machine. The RX-9 is a unit that could have problems due to the high use of relays. The real solution is to use the better DX-4D unit as they do both jobs all the time- the is 4 encoders and 4 decoders all the time. The control cable is not needed in that case as it was for encode and decode switching depending on mode. They (RX-9) are going to be costly to repair as well. The dBx units are used for NOISE REDUCTION and nothing else. They do not make the music more dynamic and if they do that is because the deck is out of calibration and is showing a double error in the record process. When you use two track you can get away with no noise reduction, when you strat mixing the noise adds up. When you get to 8 tracks you for sure need it. With 4 tracks that can be a matter of opinion and a part of the recording process. I used it in many demos I did and it worked well all the time- then again my machines were well calibrated at the time unlike some peoples' decks that can be far off and the dBx just makes it worse. The FV cable and circuit in the DX-4D can be removed and circuit disabled- I have done a few and there is no need for that cable anymore. The DX-4D can then work just fine as long as the proper nominal levels are put into it. Output levels and mixer settings. The reason a mixer or tape deck is set at what is called specified output level is that this is a setting which is giving a known output at approximately a 70% gain setting. Most mixers have a grey area on the panel at 70% area. This is put there not to make it pretty but to give indication that this is the unity gain setting of that circuit. The Unity gain setting is one where neither gain or attenuation is used for the signal. Gain adds noise as the signal is too low, attenuation is needed because the signal is too high. Due to power supply rails, it is best to stay inside of the good operating position of the power supply rather than having the decks output at max (again a gain setting) and to allow the deck to put out a sufficient signal without hitting the clipping point or that of exceeding the power supply rails that an Op Amp can handle. In studios I always set my machines up for the specified output position and then leave it there. Tape pack is one thing that the newer better machines do best. They should all be this way but over time the tape deck makers did not start all of their decks out with the most latest technology. The decks like the Tascam 52 can wind tape with little scatter. The spooling mode packs the tape as if it was just played. The Tascam 42 does the same thing but looses some control over the tape due to the arm configurations. That is why the Omega drive was made and included in the 50 and 60 series decks. All you can do on a A3440 is to use good back coated tape and to make sure the reels you use and TZ612 are in good shape and to try and not get the reel tables damaged. The tension arms need to be kept clean and edges to a minimum and polished. It can make a world of difference like when JRF gets done polishing a head stack, there is no tape handling problem when he is done and the overall performance is enhanced due to it. This does not make the tape pack different but it travels across the heads much better. Oh, the electrolytic caps should be changed prior to calibration as the better caps will make gain changes. I don't know of anyone who is willingly using 60 year old Electrolytic capacitors in their circuits. I hope this addressed all the questions you had. --- My older brother bought a 3440 new back in 1979 when I was a teenager and I remember being quite impressed with it. I have two of them, one that I bought in '94 and another that I acquired on Ebay about five years ago. I also have several Model 2A mixing boards (the 2 and 2A being the matching mixer to the A-3440, and its even better if they come with the MB-20 meter bridge). The RX-9 was the matching noise reduction unit that fits directly underneath the recorder if you remove its feet. The Ebay seller had done most of the maintenance on it, but I havent had the free time to use the recorder in a long while, so I'm hoping when I start using it again soon that I wont have to confront any major issues from it being inactive so long, other than replacing the belt which most likely will need to be done. I always thought the A-3440 was a great unit, I just love the way it looks and sounds. I have all the literature on it- brochures, manuals etc. I find it interesting that even though Tascam introduced the 34 in the early 80's, the 3440 was still in production and not discontinued. I have a Teac catalog from '84-'85, and the A-3440/2A are still shown. By the way, you can find the manufacturing date of your recorder from the serial # in the back. There is a sequence of digits and then a two digit # - for example, an 03 would mean the 3rd quarter of 198>0. (1980). A great magazine was 'Modern Recording'- I'm glad I saved all the issues I bought back in the day along with what my brother had when he subsribed- alot of good info in there on various Teac/Tascam equipment. I think the A-3440 is geared more toward home recording/multitracking, rather than as a straighforward recorder like an X-2000/1000 etc... But if anyone desires one, the A-3440 is not that difficult to find on Ebay, people are still buying them for a reasonable price. http://www.youtube.com/results?search_query=teac+a-3440 11145dee24d0a1398b0460b55fe3c7ffd876d070 0 47 1708 1683 2014-07-25T13:39:08Z Pvdm 2 wikitext text/x-wiki =Situation= <pre> cpuxxxx -> FW -> intermediateserver -> targetserver 22......-> 22 -> 22.................-> portnumber_on_targetserver </pre> =Connect= On cpuxxxx: ssh -L portnumber_on_targetserver:targetserver:portnumber_on_targetserver username_on_intermediateserver@intermediateserver '''Leave terminal open!''' Then on cpuxxxx again: ssh -YC username_on_targetserver@localhost -p portnumber_on_targetserver That's it!! =Copy files= from here tot server: scp -P portnumber_on_targetserver file user@localhost:/path/were/to/put/it/ from server to local: scp -P portnumber_on_targetserver user@localhost:/path/were/to/get/it/from/ . =mount filesystem over ssh using sshfs= sshfs user@localhost:/data/videos/ mnt/ -p portnumber =Rsync= from server to localdisk: rsync -avz -e 'ssh -p PORTNUMBER' USER@localhost:/data/htdocs/motion/ /data/motion/ =Start Konversation from behind a firewall= ssh -L 6667:irc.freenode.org:6667 user@xs3.xs4all.nl konversation --server localhost =Start Pidgin from home to wzs= * in a terminal typ: ssh -L 8300:gwmsg.wonen.amsterdam.nl:8300 root@wzs *leave terminal open *start pidgin and fill in: :server: localhost :port: 8300 =reverse tunnel= *From the machine at work, create a tunnel to your machine running ssh at home: randolf@workserver:~$ ssh -vvv randolf@myhomeserver -R 44455:localhost:22 This will forward the remote port 44455 from your home server to port 22 (or whichever port ssh is listening on) on your work machine. *From home, check to see if anything is listening on 44455 randolf@homeserver:~$ netstat -an | grep 44455 tcp 0 0 127.0.0.1:44455 0.0.0.0:* LISTEN *Next, to connect from home to your work machine, from your home server: randolf@homeserver:~$ ssh localhost -p 44455 Password: ****** From there you should be connected to your work machine via your tunnel. 98aa50addb3fd762ac2a750532b6079c3c5513b1 0 456 1720 1719 2014-08-02T07:02:30Z Pvdm 2 wikitext text/x-wiki =sox= Convert bitrate for dir: mkdir 96 # make subdir for converted files for i in *.flac; do sox "$i" "96/$i" rate 96k ; done =lplex= *Audio files must be wav or flac, dvd-compliant: **16 or 24 bit **48 or 96 khz **1-8 channels and match within each titleset. 20 bit audio is not supported. create a .ISO with files from directory: lplex -t pal -c iso -C yes -L yes -l padded *.flac <pre> -t ntsc|pal|secam -c lpcm|m2v|dvdstyler|mpeg|dvd|iso --cleanup, -C yes|no delete interim files when done. --dir, -d <dir> output everything to this directory. --dvdpath, -p <dir>|adjacent output dvd files to this directory. --workpath, -w <dir> use this folder for temporary space. --isopath, -a <dir>|adjacent output disc images to this directory. --extractpath, -E <dir>|adjacent extract to this directory. --unauthor, -u extract audio from dvd. --formatout, -f wav|flac|flac#|raw extract audio to this format. (flac equals flac8) --verbose, -v no|yes --color, -L yes|no|dark|bright --splice, -l seamless|discrete|padded|none splice the tracks together this way. How to physically structure the immediate track transition point: seamless ("concert" mode - lossless, gapless, unpadded). Track startpoints will be shifted to where audio and video frames are in alignment, ensuring gapless playback and no need for any padding between tracks. Shift direction is determined by the shift setting (see below). discrete ("compilation" mode - lossless with gaps and padding). Tracks will be padded with silence to the next full audio frame in order to pre- vent stream truncation during multiplexing. A playback gap (equal to video duration - audio duration) is introduced. An additional half-second pause will also occur during playback because of stc discontinuity. padded ("compilation" mode - lossless with padding only). Tracks will be padded with silence to the next point of a/v frame alignment. Unlike discrete there is technically neither a playback gap nor a discontinuity pause in this model, though the padding is much greater. none ("as-is" mode - lossy, unpadded, with gaps). Tracks will be padded to next dvd sample unit if required. Audio will be dropped at the end of each track, unless your files happen to be the exact length to require no truncation. The purpose of this setting is to achieve clean, efficient transitions and to avoid undesirable playback artifacts such as gaps and pops. It is not intended as an audio effect and its scope is always less than one video frame. If you want an extended pause between tracks you must include physical silence in your source audio. </pre> 1903979a6fe8da54c6cb05e8224408ece8cb5af1 0 460 1759 2014-11-04T22:30:34Z Pvdm 2 Created page with "One further question. I have a 185nWb calibration tape. Can I use it for the PR99 or should I get a 250nWb? You can use a 185nWb/m reference tape by calculating the correspo..." wikitext text/x-wiki One further question. I have a 185nWb calibration tape. Can I use it for the PR99 or should I get a 250nWb? You can use a 185nWb/m reference tape by calculating the corresponding levels to use - on page6 of this publication, there is a explanation http://home.comcast.net/~mrltapes/choo&u.pdf cce943fcb25002d7cf0a6920351ce6c8d488caa4 0 431 1762 1582 2014-11-26T12:07:10Z Pvdm 2 wikitext text/x-wiki <pre> pvdm@lapx:~> zypper lr --uri # | Alias | Name | Enabled | Refresh | URI ---+---------------------+------------------------------+---------+---------+----------------------------------------------------------------------------------- 1 | google-talkplugin | google-talkplugin | Yes | Yes | http://dl.google.com/linux/talkplugin/rpm/stable/x86_64 2 | packman-essentials | packman-essentials | Yes | Yes | http://packman.inode.at/suse/openSUSE_12.2/Essentials 3 | packman-multimedia | packman-multimedia | Yes | Yes | http://packman.inode.at/suse/openSUSE_12.2/Multimedia 4 | pvdm-fonts | pvdm-fonts | Yes | Yes | http://download.opensuse.org/repositories/home:/muzlocker/openSUSE_12.2/ 5 | pvdm-kde49 | pvdm-kde49 | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/ 6 | pvdm-kde49extra | pvdm-kde49extra | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_49_openSUSE_12.2/ 7 | pvdm-kernel | pvdm-kernel | Yes | Yes | http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ 8 | pvdm-xorg | pvdm-xorg | Yes | Yes | http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.2/ 9 | repo-non-oss | openSUSE-12.2-Non-Oss | Yes | Yes | http://download.opensuse.org/distribution/12.2/repo/non-oss/ 10 | repo-oss | openSUSE-12.2-Oss | Yes | Yes | http://download.opensuse.org/distribution/12.2/repo/oss/ 11 | repo-update | openSUSE-12.2-Update | Yes | Yes | http://download.opensuse.org/update/12.2/ 12 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss | Yes | Yes | http://download.opensuse.org/update/12.2-non-oss/ # | Alias | Name | Enabled | Refresh | URI ---+---------------------+------------------------------+---------+---------+------------------------------------------------------------------------------------- 1 | kde412 | kde412 | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Current/openSUSE_13.1/ 2 | kde412extra | kde412extra | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13.1/ 3 | kernel | kernel | No | Yes | http://ftp5.gwdg.de/pub/opensuse/repositories/Kernel:/HEAD/standard/ 4 | packman | packman | Yes | Yes | http://packman.inode.at/suse/openSUSE_13.1/ 5 | pipelight | pipelight | Yes | Yes | http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/openSUSE_13.1/ 6 | pvdm-publishing | pvdm-publishing | Yes | Yes | http://download.opensuse.org/repositories/Publishing/openSUSE_13.1/ 7 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | http://download.opensuse.org/distribution/13.1/repo/non-oss/ 8 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | http://download.opensuse.org/distribution/13.1/repo/oss/ 9 | repo-update | openSUSE-13.1-Update | Yes | Yes | http://download.opensuse.org/update/13.1/ 10 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | http://download.opensuse.org/update/13.1-non-oss/ eeadfa4d8e06ec7b516cfdc5d148964f51094476 0 30 1770 69 2014-12-15T20:14:19Z Pvdm 2 wikitext text/x-wiki * [[How to make your CUPS server broadcast itself]] *[[Install Dymo Labelwriter in openSUSE]] cf62ae793046cbe8c2d55041b6c9d7a0cc871877 0 461 1772 1771 2014-12-15T20:19:21Z Pvdm 2 wikitext text/x-wiki To install the '''Dymo Labelwriter 450''' (and probably others as well) in '''openSUSE 13.2''' (and probably others as well) do the following: #zypper in cups-devel Download the drivers from the dymo site from [http://download.dymo.com/Software/Linux/dymo-cups-drivers-1.4.0.tar.gz here] Unpack to a directory, in my case dymo-cups-drivers-1.4.0.5/ and open a terminal in that dir. Then: #./configure #make Then goto http://localhost:631 and you can add the printer and configure it as normal. Have fun! e0eb48de91989a9db0ec3481cdcf848debf8e826 0 462 1775 2015-01-08T15:42:26Z Pvdm 2 Created page with "The new openSUSE 13.2 journald (from systemd) is sometimes quickly using up disk space. There are setting you can tweak in /etc/systemd/journald.conf <pre>[Journal] Compress..." wikitext text/x-wiki The new openSUSE 13.2 journald (from systemd) is sometimes quickly using up disk space. There are setting you can tweak in /etc/systemd/journald.conf <pre>[Journal] Compress=yes SystemMaxUse=500M SystemKeepFree=2G </pre> After that, restart the services '''a few times''' for the changes to take effect: systemctl restart systemd-journald.service systemctl restart systemd-journal-flush.service You should see a reduction in the size of the /var/log/ directory almost immediately. 0070d7ca9e443e416febb0801ecc8c58cedc83bb 0 463 1777 2015-01-11T14:23:56Z Pvdm 2 Created page with "Gevonden op het audiofreaks forum: Ik heb een goede manier bedacht om plakkende banden nog goed af te spelen. Bakken is mij nooit gelukt. Band twee keer heen en weer spoelen..." wikitext text/x-wiki Gevonden op het audiofreaks forum: Ik heb een goede manier bedacht om plakkende banden nog goed af te spelen. Bakken is mij nooit gelukt. Band twee keer heen en weer spoelen buiten koppen en bandgeleiding om, dus van reel naar reel rechtstreeks. Hierbij het afslagarmpje even vastzetten. Dit doe je door een doekje heen dat vochtig is gemaakt met IPA. Dat hou je om de tape heen, lichtjes aangedrukt met je vingers. Hou de tape in het midden om aanlopen te voorkomen. Spray nu 2 a 3 pufjes WD40 op hetzelfde doekje, en bevochtig het opnieuw met IPA. Spoel nu opnieuw de tape heen en terug door je vingers met het behandelde doekje. Nu kun je de band gewoon afspelen en direct kopiëren of digitaliseren. Banden die niet meer wilden spoelen (Scotch o, a.) kan ik nu normaal afspelen en zelfs weer opnemen. Het zeer dunne laagje WD40, je moet niet overdrijven, vormt een nieuw smerend laagje. Door het afspelen wordt het ook goed verdeeld. Normaal bevat een tape ook een smeermiddel, maar dat is kennelijk na 40 jaar uitgedroogd. Maak vooraf en achteraf steeds ook de koppen schoon om de originele prut te verwijderen. WD40 droogt uiteindelijk volledig in en integreert met het tape oppervlak. Het geeft in mijn ervaring niet af of zo. Experimenteer eerst eens met een onbelangrijke plakkende tape. Zelf heb ik alleen maar succes hiermee gehad. Bron: Sterremuur op het forum audiofreaks.nl d85d177f12c939d46c4e77eaa59d45c5ed131f10 0 464 1779 2015-01-15T08:27:55Z Pvdm 2 Created page with "<pre> [NU] NUUrl = https://nu.novell.com/ NURegUrl = https://secure-www.novell.com/center/regsvc/ NUUser = XXXXXXXXXXXXXXXXXXXX NUPass = XXXXXXXXXXXXXXXXXXX [DB] config = dbi..." wikitext text/x-wiki <pre> [NU] NUUrl = https://nu.novell.com/ NURegUrl = https://secure-www.novell.com/center/regsvc/ NUUser = XXXXXXXXXXXXXXXXXXXX NUPass = XXXXXXXXXXXXXXXXXXX [DB] config = dbi:mysql:database=smt;host=localhost user = smt pass = XXXXXXXXXXXXXXXXXXXXXX [LOCAL] # Default should be http://server.domain.top/ url = XXXXXXXXXXXXXXXXXXXXX # This email address is used for registration at NCC nccEmail = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX MirrorTo = /data/smt MirrorAll = false MirrorSRC = false forwardRegistration = true rndRegister = 331 # specify proxy settings here, if you do not want to use the global proxy settings # If you leave these options empty the global options are used. # # specify which proxy you want to use for HTTP connection # in the form http://proxy.example.com:3128 HTTPProxy = # specify which proxy you want to use for HTTPS connection # in the form http://proxy.example.com:3128 HTTPSProxy = # specify username and password if your proxy requires authentication # in the form username:password ProxyUser = # # require authentication to access the repository? # Three possible authtypes can be configures here # 1) none : no authentication required (default) # 2) lazy : check only username and password. A valid user has access to all repositories # 3) strict : check also if this user has access to the repository. # requiredAuthType = none # # the smt commands should run with this unix user # smtUser = smt # # ID of the GPG key to be used to sign modified (filtered) repositories. # The key must be accessible by the user who runs SMT, i.e. the user specified # in the 'smtUser' configuration option. # # If empty, the modified repositories will be unsigned. # signingKeyID = [REST] # Enable administrative access to the SMT RESTService by setting enableRESTAdminAccess=1 # default: 0 enableRESTAdminAccess = 0 # Define the username the REST-Admin uses for login # default: RESTroot RESTAdminUser = RESTroot # Define the password for the REST-Admin (note: empty password is invalid) # default: <empty> RESTAdminPassword = [JOBQUEUE] # maximum age of finished (non-persistent) jobs in days # default: 8 maxFinishedJobAge = 8 [REPORT] # comma separated list of eMail addresses where the status reports will be sent to reportEmail = XXXXXXXXXXXXXXXXXXXXXX # from field of report mails - if empty it defaults to "root@<hostname>.<domainname>" reportEmailFrom = # relay mail server - leave emtpy if mail should be sent directly mailServer = mailServerPort = # mail server authentication - leave empty if not required mailServerUser = mailServerPassword = 758f95710e2ad19b2ed436d40fe71258fcdf7683 0 465 1784 1783 2015-01-22T14:28:53Z Pvdm 2 wikitext text/x-wiki Identificatie van tapes Geen aanloopstrook: tja... wit met paars/blauwe blokjes en 150 = TDK Audua kant 1 wit met rode blokjes en 150 = TDK Audua kant 2 TDK Audua tape is vrij donker van kleur, aanloopstroken vallen er vaak af transparant/wit met zwart raster en LX35 of GX35 = TDK LX of GX kant 1 transparant/wit met rood raster en LX35 of GX35 = TDK LX of GX kant 2 TDK LX kan met en zonder backcoating, erg glad en vrij donker van kleur TDK GX altijd met backcoating, vrij glad en iets lichter van kleur als LX transparant wit met grijze blokjes = Maxell LN/Communicator kant 1 transparant wit met oranje blokjes = Maxell UD tot 1982 kant 1 transparant wit met blauwe blokjes = Maxell UD vanaf 1982 kant 1 transparant wit met blauwe cijfers 50/35/25/18 = Maxell UD vanaf 1988 kant 1 transparant wit met zwarte blokjes = Maxell UDXL kant 1 transparant wit met donkergroene blokjes = Maxell XLI kant 1 transparant wit met donkergroene cijfers 50/35 = Maxell XLI vanaf 1988 kant 1 transparant wit met gouden blokjes = Maxell XLII (EE) kant 1 transparant wit met gouden cijfers = Maxell XLII (EE) vanaf 1988 kant 1 transparant wit met rode/roze blokjes = Maxell kant 2 transparant met kleine, rode stippeltjes: Maxell UD 50/35/25/18 en XLI 50/35 vanaf 1988 kant 2 ruiken allemaal hetzelfde wit met zwarte letters SONY = Sony tape kant 1 wit met blauwe letters SONY = Sony tape kant 1 (blijkt ook voor te komen) wit met rode letters SONY = Sony tape kant 2 groen met zwarte binnenkant en opdruk met cijfers en SPR50, LPR35 of DPR26 = BASF LH Professional kant 1 rood met zwarte binnenkant zonder opdruk = BASF LH Professional kant 2 groen met cijfers en SP50, LP35, DP26 of TP18 met schakelfolie = BASF > zie aanduiding op strook rood zonder cijfers met schakelfolie = BASF kant 2 BASF SP/LP/DP/TP is roodbruin van kleur en heeft een redelijk sterke geur lichtgroen met schakelfolie op de strook = Scotch LP lichtblauw met schakelfolie op de strook = Scotch DP lichtrood/roze met schakelfolie op de strook = Scotch kant 2 Scotch tape is donker/zwart van kleur en heeft een sterke (ietwat zoete) geur. Ook herkenbaar aan de montage van de aanloopstrook aan de tape; deze laat meestal iets los en vouwt om. Dezelfde aanloopstrook komt voor bij Revox tapes. Revox maakt gebruik van Scotch tape en Ampex tape. Plakt het en is het bruin van kleur, dan is het Ampex; plakt het niet of minder en is het donker van kleur, dan is het Scotch tape. donkergroen transparant = Ampex kant 1 donkerrood transparant = Ampex kant 2 geen schakelfolie, tape is bruinig van kleur, met backcoating Bij Maxell staat het getal op de aanloopstrook voor de dikte van de tape in micron. Bij BASF staat het getal eveneens voor de dikte in micron; LP is long play en DP is double play. LPR en DPR: idem maar dan LH Professional. Bij TDK en Sony staat getal voor de lengte van de tape in aantal % t.o.v. een SP (standard play) tape. Standard play lengte bij 26,5cm is 2400 feet, long play is 3600 feet, dus 150% van standard play. (Met dank aan Andreas, die mij dit lijstje ooit eens stuurde ;) ) (bron: analogaudio.nl forum) ed6c68e7367f0a958a620181c43b03c47b2cdd57 0 466 1788 1787 2015-02-02T17:00:12Z Pvdm 2 wikitext text/x-wiki BASH for loop works nicely under UNIX / Linux / Windows and OS X while working on set of files. However, if you try to process a for loop on file name with spaces in them you are going to have some problem. For loop uses $IFS variable to determine what the field separators are. By default $IFS is set to the space character. There are multiple solutions to this problem. =Set $IFS variable= Try it as follows: <pre> #!/bin/bash SAVEIFS=$IFS IFS=$(echo -en "\n\b") for f in * do echo "$f" done IFS=$SAVEIFS </pre> OR <pre> #!/bin/bash SAVEIFS=$IFS IFS=$(echo -en "\n\b") # set me FILES=/data/* for f in $FILES do echo "$f" done # restore $IFS IFS=$SAVEIFS </pre> =More examples using $IFS and while loop= Now you know that if the field delimiters are not whitespace, you can set IFS. For example, while loop can be used to get all fields from /etc/passwd file: <pre>.... while IFS=: read userName passWord userID groupID geCos homeDir userShell do echo "$userName -> $homeDir" done < /etc/passwd </pre> source: http://www.cyberciti.biz/tips/handling-filenames-with-spaces-in-bash.html 9a6313d895cc719c30b0498c2cdbc3104def317a 0 467 1790 2015-02-02T17:02:40Z Pvdm 2 Created page with "In Linux, find running dd processes and send them a signal to print out their progress. kill -USR1 $( pidof dd )" wikitext text/x-wiki In Linux, find running dd processes and send them a signal to print out their progress. kill -USR1 $( pidof dd ) 38f5834b2787dd3b19fc89dede558afceba844d5 0 469 1794 2015-02-03T20:20:55Z Pvdm 2 Created page with "Sort installed RPMs by size To list all RPM packages installed on a Linux machine sorted from the largest to the smallest in size: rpm -qa --queryformat '%{size} %{name}\n'..." wikitext text/x-wiki Sort installed RPMs by size To list all RPM packages installed on a Linux machine sorted from the largest to the smallest in size: rpm -qa --queryformat '%{size} %{name}\n' | sort -rn | more 6a0f79f3bf28f829f1e41454f59c6680524ccf52 0 470 1798 2015-02-18T17:44:48Z Pvdm 2 Created page with "*[[command line tips]]" wikitext text/x-wiki *[[command line tips]] 5af3e838aa33911644b1bc63691b3892be48ff00 0 471 1800 1799 2015-02-18T17:47:12Z Pvdm 2 wikitext text/x-wiki Show all VMs: vboxmanage list -l vms Show the state of the VM: vboxmanage showvminfo w7new | grep State Control the state of the VM: vboxmanage controlvm w7new pause|resume|reset|poweroff|savestate| acpipowerbutton|acpisleepbutton 3df38544986b22f6b3e7c130be007e476decd6b3 0 426 1807 1806 2015-02-27T15:39:44Z Pvdm 2 wikitext text/x-wiki = [http://pvdm.xs4all.nl/philip/index.php?categoryid=1&p2_articleid=7 Linux - MythTV - Technotrend - DVB-C - Ziggo] = Na de aanschaf van een mooie HD-TV, die overigens zijn eigen problemen heeft, maar daar zal ik het maar niet over hebben (-update: alles is ok, een firmware update doet wonderen!) is het toch wel een flinke stap terug om de opnamen van MythTV te bekijken, die zijn gemaakt met een analoge tv-tunerkaart. Ik weet dat het een '''slangenkuil''' is waarin ik me begeef, maar 'no guts, no glory!', dus we gaan het proberen. Wat zijn de problemen? Allereerst moet de backend (die de opnamen doet) draaien op linux, bij voorkeur op openSUSE. Dat is met MythTV geen enkel probleem, maar de keuze voor linux heeft wel heel veel implicaties voor de rest van de setup, en met name de hardware. Ik moet een DVB-C (Digital Video Broadcasting - Cable) setup zien te vinden die door de linux kernel gesupport wordt. Daar bovenop moet dit dan ook nog eens compatibel zijn met de digitale standaard waarin Ziggo uitzend, en dan OOK nog de gebruikte encryptie (Irdeto) ondersteunen! Op het internet zijn weinig (geen) succesvolle verhalen te vinden over deze combinatie van factoren, dus het wordt interessant, zeg maar. Het zou best kunnen dat het geheel niet gaat werken. Op deze pagina [link is weg] staat een overzicht van de kaarten die in de kernel zitten. Ik heb gekozen voor de Technotrend 1501, vanwege de beschikbaarheid in Nederland, en deze forumpost die beweert dat hij goed werkt met mijn 'omstandigheden'. Er zit een CAM module bij. Ik hoop dat mijn keuze voor een AlphaCrypt Light module in combinatie met de '''Ziggo''' smartcard ook goed gaat werken. Verder besluit ik om de nieuwste '''MythTV''' (0.24) te gaan gebruiken, want er wordt steeds meer en steeds betere ondersteuning voor DVB in MythTV ingebouwd. == De eerste stap - het upgraden van openSUSE 11.2 naar 11.3 == Eerst de server naar versie 11.3 gebracht, dit moest toch gebeuren. Dit is via de '#zypper dup' methode super makkelijk. Zie hiervoor de openSUSE wiki. Na de upgrade heb ik getest of alles nog werkt zoals hiervoor (website, MySQL, etc.), en dit bleek het geval. Al met al een succesvolle, simpele upgrade.Hierna heb ik nog een extra stap gedaan: ik heb de nieuwste kernel erin gehangen via een extra repo. Ik draai nu de 2.6.36 kernel i.p.v. de standaard 2.6.34.&nbsp; == De tweede stap - MythTV upgraden naar 0.24 == Het upgraden van MythTV heeft wat meer voeten in de aarde. Packman heeft het pakket in zijn repo, maar al met het versienummer *in* de pakketnaam, als in 'mythtv-0_21-backend'. Een simpele '#zypper up' werkt hier dus niet, het zijn voor je packetmanager 2 verschillende pakketten. Dus ik &nbsp;moest de ene deinstalleren, en de andere installeren. Ik heb de volgende rpm's handmatig gedownload en in een directory gezet: <pre> mytharchive-0_24-0.24-0.pm.5.1.x86_64 mythtv-0_24-setup-0.24-0.pm.5.1.x86_64 mythtv-0_24-backend-0.24-0.pm.5.1.x86_64 python-MythTV-0_21-0.21-29.pm.30.3.noarch mythtv-0_24-base-themes-0.24-0.pm.5.1.noarch mythtv-0_24-docs-0.24-0.pm.5.1.x86_64 mythtv-0_24-common-0.24-0.pm.5.1.x86_64 libmyth-0_24-0.24-0.pm.5.1.x86_64 mythtv-0_24-frontend-0.24-0.pm.5.1.x86_64 mythweb-0_24-0.24-0.pm.5.1.x86_64 </pre> Mythbackend gestopt en de rpm's met '#zypper in *.rpm' geinstalleerd. Ik moest een heleboel dependencies oplossen (natuurlijk). Ik koos steeds voor 'deinstallation of ...0.21 version' waardoor de 0.24 versie de 0.21 versie overschrijft. Het lijkt vervelend maar maakt allemaal sense en is ook wel logisch. Na afloop heb ik de nieuwe versie. Komende vanuit mijn versie 0.21 moest eerst de MySQL database geupgrade worden, voordat ik de backend weer kon starten, zie hiervoor de MythTV wiki. Dit is overigens nog een heel gedoe, maar daar ga ik hier niet over uitwijden.Toen dat succesvol gedaan was, heb ik de backend weer gestart en toen had ik de nieuwe MythTV! Nadat MythTV naar de laatste versie is gebracht heb ik dat getest door een opname te maken met de kaart die er dan nog in zat, de analoge Hauppauge PVR-350. Alles werkte nog gewoon, dus ik ging verder met de volgende stap. == De derde stap - het installeren van de DVB kaart van Technotrend == Computer uitgezet, PVR-350 eruit en Technotrend C-1501 + CAM module + Ziggo smartcard erin, Computer weer aan. Even kijken in dmesg of de kaard herkend wordt en jawel hoor, de kernel herkent hem gewoon. In MythTV kon ik gewoon een New Capture Card toevoegen: <pre> Card Type: DVB DTV capture card (v3.x) <nowiki>DVB device number: /dev/dvb/adapter0/frontend0 <- dit werd automatisch ingevuld</nowiki> </pre> Kies recording options: <pre> Max recordings: 1 v wait for SEQ start header v open DVB card on demand v Use DVB card for active EIT scan&nbsp; </pre> Verder moest ik MythTV inrichten zoals bij elke andere kaart. Maar hierna kwam het scannen naar de zenders.Nadat ik een video source had toegevoegd, kon ik bij Input Connections kiezen voor deze videosource. Als je dat dan kiest kom je bij scan for channels.Scan configuration: <pre> Desired Services: TV v unencrypted only Scan Type: Full Scan (Tuned) Frequency: 372000000 Symbol Rate 6875000 Modulation QAM 64 </pre> Deze gegevens zijn overigens gewoon te vinden in het foldertje wat je bij je Ziggo smartcard krijgt. Nadat het kaartje alle zender gevonden had, ik geloof dat het er 166 waren, ben ik in de Channel Editor gedoken en heb alles goed afgeconfigureerd. Tip: ook via de mythweb interface kun je makkelijk de zendertabel editten! = mysql = make database dump: mysqldump -u root -p –all-databases > pvdm.sql mysqldump -u root -p wikidb > pvdm.sql restore the dump: <nowiki>#mysql -u root -p</nowiki> mysql> create database xyz; mysql> quit; <nowiki>#mysql -u root -p [dbname] < pvdm.sql</nowiki> delete database: <nowiki>#mysql -u root -p</nowiki> mysql> drop database xyz; = update 18 feb 2015= Zodra u gaat zoeken naar zenders vraagt uw ontvanger of TV naar de frequentie en het netwerk-ID. Gebruik altijd frequentie 474.00 en netwerk-ID 5555. Overige gegevens zoals modulatie en symboolsnelheid hoeft u niet aan te passen. Sommige digitale ontvangers of CI+ televisies hebben een extra 0 of juist een 0 minder nodig. Bijvoorbeeld 474.000 of 05555. Uw apparaat laat dit zien zodra u gevraagd wordt om de gegevens in te vullen. Welke modellen dit precies zijn vindt op deze pagina. ==Wat zijn ongecodeerde kanalen?== Wij versleutelen standaard onze digitale televisiekanalen. Uw smartcard zorgt ervoor dat de versleutelde kanalen in uw abonnement zichtbaar worden voor uw TV. Na de werkzaamheden verandert dit. Vanaf dat moment zijn meer dan 30 kanalen uit het standaardpakket beschikbaar zonder smartcard. We noemen dat ongecodeerde kanalen. Dit is bijvoorbeeld erg handig als u ook op uw tweede of derde televisie digitale TV wil kijken. U hoeft hier dan niet perse een nieuwe smartcard voor te kopen. In het zenderoverzicht ziet u om welke zenders het gaat. https://www.ziggo.nl/televisie/zenderoverzicht-nieuw ==update 27 februari 2015== Op Philips TV's met aankoopdatum 2010 t/m 2012 zal de HD zendervolgorde met het netnummer 5555 niet werken zoals het door Ziggo/UPC is ingevoerd en daarom hebben zij voor meerdere regio's alternatieve netnummers beschikbaar gesteld. Die meerdere regio's zijn: Alkmaar 43192 - Alphen a/d Rijn 43185 - Amersfoort 43195 - Breda 43191 - Capelle 43194 - Den Bosch 43198 - Den Haag 43186 - Driebergen 43189 -Emmen 43208 - Gorinchem 43190 - Gorredijk 43209 - Groningen 43206 - Hengelo 43211 - Hilversum 43196 - Hoogeveen 43205 - Mill 43197 - Utrecht 43187 - Roosendaal 43199 - Roermond 43202 - Sassenheim 43184 - Schoonbron 43203 - Sneek 43210 - Tilburg 43200 - Veenendaal 43188 -Velsen 43193 - Venlo 43201 - Winschoten 43207 - Zwolle 43204 aac0f294a5de75a4daa5c7d9ed22d796ad2081d0 0 474 1821 2015-03-01T11:32:34Z Pvdm 2 Created page with "*[[brute force test wordpress]]" wikitext text/x-wiki *[[brute force test wordpress]] 08afbed62d00d30acd8f8418ecde5d19dec1dd63 0 475 1822 2015-03-01T11:33:59Z Pvdm 2 Created page with " nmap -p 80 --script http-wordpress-brute --script-args http-wordpress-brute.threads=4,http-wordpress-brute.uri="/blog/wp-login.php" <target>" wikitext text/x-wiki nmap -p 80 --script http-wordpress-brute --script-args http-wordpress-brute.threads=4,http-wordpress-brute.uri="/blog/wp-login.php" <target> 2bf0a72d07c37df0801d803b29d2870d63e3d50d 0 476 1824 2015-03-02T19:36:07Z Pvdm 2 Created page with "*[[creating an wave sequence]]" wikitext text/x-wiki *[[creating an wave sequence]] a5bf95fa684af8568245ec0881dcbdf0d7916faf 0 477 1827 1826 2015-03-02T19:41:45Z Pvdm 2 wikitext text/x-wiki Wave Sequence This option is used to run a sequence of waveforms under a timer control. * Affected parameters are function (Sine, Square, Triangle or Library waveform), frequency, offset and amplitude for each step. * The sequence may contain any number of steps. * The command strings may be entered manually, loaded from a text file or received through the serial port. The data file is a normal text file. It can be edited using standard text editors or the editor of this option. At the startup there is an example file for editing in the edit window . * When entering the data use Tab as a separator (do not use spaces). * Use Save as option of the File menu to save the file. * Click Open button to open a file. * Click Run button to execute the sequence file. * Select Repeat check box to repeat the sequence over and over again. * Click Exit to break the execution. The file contains on each line following data: * Function [1, 2, 3, 4 or 0] * Frequency [Hz] * Offset [V] * Output voltage [Vpp] * Time [s] * File name (*) (Only if function number 4 is selected) Note: If the Time parameter is set to 0 then the generator outputs the waveform until you click the Next Step button or press Enter or the Space Bar. Function selection 1 = Sine 2 = Square 3 = Triangle 4 = Library waveform 0 = No change (The previous selected waveform is used.) Example of the file <pre> 1 12000 -1.5 7.5 30 2 24000 0 5.5 60 4 400 5 10 20 burst01.lib 0 500 4 9 15 Line 1: Generator outputs sine wave at 12000Hz, -1.5V offset and 7.5Vpp output voltage for 30 seconds. Line 2: Generator outputs square wave at 24000Hz, 0V offset and 5.5Vpp output voltage for 60 seconds. Line 3: Generator outputs library waveform "burst01.lib" at 400Hz, 5V offset and 10Vpp output voltage for 20 seconds. Line 4: Generator outputs library waveform "burst01.lib" at 500Hz, 4V offset and 9Vpp output voltage for 15 seconds. </pre> Receiving the command strings through the serial port In this mode you can remote control the operation of the function generator. * Select Serial Port radio button in the Source Data box. * Set the communications parameters such as COM port, baud rate, data bits, stop bits and parity. * The software is ready to receive the command strings from the serial port. * If the Time parameter is set to 0 then the generator outputs the selected waveform until the next instruction is received from the serial port. Note: Make sure that the library waveform files are located in the Lib subfolder of the PcLab2000LT program folder (normally C:\ProgramFiles\Velleman\PcLab2000LT\lib). c4dd54f13e8dd2c8421d39e968c82c39d16b982d 0 478 1829 2015-03-04T08:33:43Z Pvdm 2 Created page with "*[[find latest files in all subdirectories per directory]]" wikitext text/x-wiki *[[find latest files in all subdirectories per directory]] 4ba8aa4428904be6da2e3bea3ca6f8803318ab3f 6 481 1842 2015-03-27T10:53:12Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 438 1843 1614 2015-03-27T10:56:22Z Pvdm 2 Pvdm uploaded a new version of [[File:Tux-blink.gif]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 480 1845 1841 2015-04-05T19:16:32Z Pvdm 2 wikitext text/x-wiki output since booting: journalctl -b Follow: journalctl -f Keep an eye on sshd service: journalctl -b -f -l -u sshd Examples: journalctl -b --system journalctl -b --user journalctl --since=yesterday journalclt -b _PID=1 journalclt -b _UID=1001 journalclt -b /usr/bin/sudo journalctl KERNEL_DEVICE=+scsi:0:0:0:0 -x -> extra info To monitor the output of dmesg: # journalctl -kf or # dmesg -wH 88f2d222e8178d380604ea5245048d96fa3626cb 0 406 1851 1441 2015-07-16T06:51:14Z Pvdm 2 wikitext text/x-wiki === TECHNISCHE SPECIFICATIES VAN DE SAMSUNG RV720-S02NL === {| style="border-spacing:0;" | colspan="2" style="background-color:#dddddd;"| '''Product''' |- || Fabrikantcode || NP-RV720-S02NL |- || Artikelnummer || 140137 |- || Garantie || 2 jaar |- || Garantietype || Pick-up-and-return-garantie |- | colspan="2" style="background-color:#dddddd;"| '''Processor''' |- || Processor || Intel Core i5 |- || Processornummer || 2410M |- || Processorkernen || Dual Core[[Image:alternatives_icon_static.gif]] |- || Kloksnelheid || 2300 MHz |- | colspan="2" style="background-color:#dddddd;"| '''Geheugen''' |- || Intern RAM-geheugen || 4 GB[[Image:alternatives_icon_static.gif]] |- || Type geheugen || SO-DIMM DDR3-1333 |- | colspan="2" style="background-color:#dddddd;"| '''Harde schijf''' |- || Opslagcapaciteit || 640 GB[[Image:alternatives_icon_static.gif]] |- || Type harde schijf || SATA |- || Hardeschijfsnelheid || 5400 rpm |- || Aantal schijven (intern) || 1 |- | colspan="2" style="background-color:#dddddd;"| '''Beeldscherm''' |- || Schermdiagonaal || 17,3 inch[[Image:alternatives_icon_static.gif]] |- || Schermdiagonaal || 17,3 inch |- || Resolutie || 1600 x 900[[Image:alternatives_icon_static.gif]] |- || Schermtype || TFT-LCD met LED-achtergrondverlichting |- || Type beeldscherm || Glanzend[[Image:alternatives_icon_static.gif]] |- || High Definition || [[Image:false_icon.gif]][[Image:alternatives_icon_static.gif]] |- || 3D || [[Image:false_icon.gif]] |- || Touchscreen || [[Image:false_icon.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Videokaart''' |- || Videokaartfamilie || NVIDIA GeForce[[Image:alternatives_icon_static.gif]] |- || Type videokaart || '''NVIDIA GeForce GT 520M''' |- || Videogeheugen || 1024 MB |- | colspan="2" style="background-color:#dddddd;"| '''Optische drive''' |- || DVD-speler/brander || DVD-speler & -brander[[Image:alternatives_icon_static.gif]] |- || Blu-ray || [[Image:false_icon.gif]][[Image:alternatives_icon_static.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Communicatie''' |- || Ethernetsnelheid || 1000 Mbit/s (Gigabit Ethernet)[[Image:alternatives_icon_static.gif]] |- || Wi-Fi || [[Image:true_icon.gif]] |- || Wifi-standaard || 802.11b, 802.11g, 802.11n |- || Bluetooth || [[Image:true_icon.gif]][[Image:alternatives_icon_static.gif]] |- || RJ11 Modem || [[Image:false_icon.gif]] |- || Ingebouwde 3G modem || [[Image:false_icon.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Audio''' |- || Microfoon intern || [[Image:true_icon.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Camera''' |- || Webcam || [[Image:true_icon.gif]][[Image:alternatives_icon_static.gif]] |- || Webcam resolutie || VGA (0.3 Megapixel) |- | colspan="2" style="background-color:#dddddd;"| '''Bediening''' |- || Toetsenbordindeling || QWERTY[[Image:alternatives_icon_static.gif]] |- || Backlit toetsenbord || [[Image:false_icon.gif]] |- || Numeriek keypad || [[Image:true_icon.gif]][[Image:alternatives_icon_static.gif]] |- || Touchpad || [[Image:true_icon.gif]] |- || Multi-Touch || [[Image:true_icon.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Aansluitingen''' |- || e-SATA || [[Image:false_icon.gif]] |- || ExpressCard || [[Image:false_icon.gif]] |- || HDMI || [[Image:true_icon.gif]][[Image:alternatives_icon_static.gif]] |- || Aantal USB-poorten || 3 |- || USB-versie || 2.0[[Image:alternatives_icon_static.gif]] |- || VGA || [[Image:true_icon.gif]] |- || 3,5 mm Audio || [[Image:true_icon.gif]] |- || 3,5 mm Microfoon || [[Image:true_icon.gif]] |- || Geheugenkaartlezer || [[Image:true_icon.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Beveiliging''' |- || Trusted Platform Module (TPM) || [[Image:false_icon.gif]] |- || Vingerafdruksensor || [[Image:false_icon.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Accu''' |- || Accu || [[Image:true_icon.gif]] |- || Aantal cellen || 6 |- | colspan="2" style="background-color:#dddddd;"| '''Software''' |- || Besturingssysteem || Windows 7 Home Premium[[Image:alternatives_icon_static.gif]] |- || Versie besturingssysteem || 64 bit |- || Taal besturingssysteem || Nederlands, Engels |- | colspan="2" style="background-color:#dddddd;"| '''Fysieke eigenschappen''' |- || Lengte || 27,51 cm |- || Breedte || 42 cm |- || Dikte || 2,9 cm |- || Gewicht || 2680 g |- || Gewicht || van 2,5 tot 3 kilo[[Image:alternatives_icon_static.gif]] |- || Kleur || Zilver[[Image:alternatives_icon_static.gif]] |- | colspan="2" style="background-color:#dddddd;"| '''Overige''' |- || Merk || Samsung[[Image:alternatives_icon_static.gif]] |- || Gebruik || Media & Entertainment[[Image:alternatives_icon_static.gif]] |} 88c4049152844c5046868b80a8d8d7974a19aefc 0 387 1853 1434 2015-07-16T06:55:33Z Pvdm 2 wikitext text/x-wiki *[[specs samsie]] *[[partitions samsie]] *[[grub samsie]] *[[repos]] *[[fix grub]] dc1b9aa3a9a1a8091498de6350a4b0a95ad1187d 0 459 1855 1741 2015-07-29T08:42:41Z Pvdm 2 wikitext text/x-wiki =awk= pattern {action} pattern {action} $ awk '{print $2}' /etc/fstab to filter out comment lines - starting with # $ awk '/^[^#]/ {print $2}' /etc/fstab to grep on TWO occurences (AND operator) $ awk '/pattern1/ && /pattern2/' /var/log/messages case insensitive $ awk '/pattern1/ && /pattern2/' IGNORECASE=1 /var/log/messages print first field from password file using field seperator ':' $ awk -F: '{print$1}' /etc/passwd print only user ID > 500 $ awk -F: '$3>=500 {print$1}' /etc/passwd display average of numbers entereed on a line: $ awk '{ sum=0; for (i=1; i<=NF; i++) sum +=$i; print sum/NF; }' {| |- | NF || number of fields in the current line |- | NR || the current record number (line number) |- | FS || input field seperator (space by default) |- | RS || record seperator (newline by default) |- | Example || Example |- | Example || Example |- | Example || Example |- | Example || Example |- | Example || Example |} show the 5th record on the second line: df /tmp | awk 'NR==2 {print$5 }' ==use awk with a program== the file '''maxuid''': <pre>BEGIN {maxuid = 0; FS=":" } { if ($3 > maxuid) maxuid = $3 } END { print" the largest UID is ", maxuid } </pre> then use awk like this: $ awk -f maxuid /etc/passwd to ignore user nobody: <pre>BEGIN {maxuid = 0; FS=":" } $1 != "nobody" { if ($3 > maxuid) maxuid = $3 } END { print" the largest UID is ", maxuid } </pre> cat -n: (adds line numbers) $ awk '{ print NR, $0}' /etc/fstab wc -w: (count words) $ awk '{ w += NF } END { print w}' /etc/fstab grep chris /etc/passwd: $ awk '/^chris/' /etc/passwd ==writing self contained scripts== <pre> #!/usr/bin/awk -f { cost[$1] += $2*$4 } END { for (cat in cost) print cat, cost[cat] } </pre> chmod u+x catscript ./catscript http://www.pement.org/awk/awk1line.txt 8a73482f86a9bb881570ed1759340c3dfae19de3 0 458 1858 1857 2015-08-11T16:33:43Z Pvdm 2 wikitext text/x-wiki * fuser -ck /net pid of proccess holding mount openssl x509 -noout -in scx-host-sldbowzs0101.basis-a.acc.pem -text <syntaxhighlight lang="python"> def quickSort(arr): less = [] pivotList = [] more = [] if len(arr) <= 1: return arr else: </syntaxhighlight> <syntaxhighlight lang="bash"> def quickSort(arr): less = [] pivotList = [] more = [] if len(arr) <= 1: return arr else: </syntaxhighlight> 0854c48423c3973ba97a46d800442529c80917d1 0 123 1860 1859 2015-08-11T16:35:35Z Pvdm 2 wikitext text/x-wiki <syntaxhighlight lang="bash"> #!/bin/bash # ------------------------------------------------------------------------- # Copyright (c) 2003 nixCraft project <http://cyberciti.biz/fb/> # This script is licensed under GNU GPL version 2.0 or above # ------------------------------------------------------------------------- # This script is part of nixCraft shell script http://en.wikipedia.org/wiki/Shell_script collection (NSSC) # Visit http://bash.cyberciti.biz/ for more information. # Copyright (c) 2010 CyberOrg Info. Modification to watch any process/service # ------------------------------------------------------------------------- RESTART="/etc/init.d/sshd restart" PGREP="/usr/bin/pgrep" processtowatch="sshd" x=1 while [ $x = 1 ]; do # find pid $PGREP ${processtowatch} if [ $? -ne 0 ] then echo "`date` : $processtowatch went down, restarting" >> /var/log/restart.log $RESTART fi sleep 30 done </syntaxhighlight> fbf26c323bd499ca0945362052b10bcf16715a5d 0 412 1861 1455 2015-08-11T16:36:33Z Pvdm 2 wikitext text/x-wiki *To test the speed of the filesystem (not the physical disk!) you can use the following script: <syntaxhighlight lang="bash"> #!/bin/bash # USAGE: # ./speed_test.sh /path/to/my/file /path/to/destination number_of_tests NUM_TESTs=$3 SUM=0 for i in $( seq 1 $NUM_TESTs ); do REC=`dd if=$1 of=$2 2> some_random_file_ ; cat some_random_file_ | cut -d " " -f8 | tail -1` SUM=`echo $SUM + $REC | bc` done RESULT=`echo $SUM / $NUM_TESTs | bc | awk '{ str1=str1 $0 }END{ print str1 }'` echo $RESULT MB/s #clean up rm some_random_file_ rm $2 </syntaxhighlight> *To make a big file, use cat /dev/zero > zerofile and abort it with CTRL-C after a few seconds. Alternatively, you can use something like dd if=/dev/zero of=file.out bs=1MB count=500 to create a 500MB file. *Start the script like this: ./speed_test.sh /mnt/sda1/zerofile /mnt/sdb1/zerofilecopy 3 The result will be something like ./speed_test.sh ./zerofile ./2delete 5 237 MB/s f346ad3807109f69e506b777e68289ba62550de8 0 479 1862 1831 2015-08-11T16:38:26Z Pvdm 2 wikitext text/x-wiki Create a file latestfile.sh: <syntaxhighlight lang="bash"> #!/bin/bash ls -lrt "$1" | tail -n1 </syntaxhighlight> Make it executable chmod +x ./latestfile.sh Then execute the following command: find . -mindepth 1 -type d -printf "%T+ %p/" -exec ./latestfile.sh {} \; Output: <pre> 2015-02-07+04:01:53.0000000000 ./$RCE/SLES11-SP2-Updates/sle-11-i586/repodata/repomd.xml.key 2015-02-07+04:02:09.0000000000 ./$RCE/SLES11-SP2-Updates/sle-11-i586/repodata 2015-02-07+04:07:41.0000000000 ./$RCE/SLES11-SP3-Pool/sle-11-i586/.repodata/repomd.xml.key 2015-02-07+04:07:41.0000000000 ./$RCE/SLES11-SP3-Pool/sle-11-i586/rpm </pre> When outputted to a file (list.txt) then you could follow up with: cat list.txt | grep -v repomd | grep rpm | sort 3eafc7c957fc771c9635fc6eaabd740d9da76361 0 483 1875 1874 2015-09-03T05:58:14Z Pvdm 2 wikitext text/x-wiki testdatabase 'testsietske'; <pre> > mysql -u root MariaDB [testsietske]> use testsietske; MariaDB [testsietske]> show tables; MariaDB [testsietske]> select * from City; MariaDB [testsietske]> select * from City where Countrycode = "NLD"; MariaDB [testsietske]> select * from City where District = "Noord-Holland"; MariaDB [testsietske]> select * from City where Countrycode = "NLD" and population > "100000"; MariaDB [testsietske]> show tables; MariaDB [testsietske]> select * from Country where Continent = "Europe"; ---- </pre> * You can use db_name.tbl_name as an alternative to the tbl_name FROM db_name syntax. In other words, these two statements are equivalent: <pre> SHOW COLUMNS FROM City; MariaDB [testsietske]> SHOW COLUMNS FROM mytable FROM mydb; MariaDB [testsietske]> SHOW COLUMNS FROM mydb.mytable; </pre> * show only first 10 results <pre> MariaDB [testsietske]> select * from City limit 10; </pre> * show result 10 to 30 <pre> MariaDB [testsietske]> select * from City limit 20 offset 10;</pre> bc295eef6f81d8ed955718155b9d3bd9d53b94c2 0 424 1893 1546 2015-11-08T20:40:58Z Pvdm 2 wikitext text/x-wiki Now this may or may not be specific to openSUSE, but here it is anyway: I suffered from desktop lockups when copying large files, for instance from the wireless network to usb. THis was especially noticable in dolphin. Even though I suspected it at first, now it appears that it is not dolphin that is acting up, it is the 'hugepage' option in the kernel. So, how do we tweak it? Simpel. The following lines will do the trick as root: echo never >/sys/kernel/mm/transparent_hugepage/defrag echo 0 > /sys/kernel/mm/transparent_hugepage/khugepaged/defrag -edit- echo never > /sys/kernel/mm/transparent_hugepage/enabled echo madvise > /sys/kernel/mm/transparent_hugepage/enabled e3c750b89affe093ebd3d67395c2e2cf2e3aaeaa 0 488 1910 2015-11-22T08:51:20Z Pvdm 2 Created page with " rc.d/after.local:su - qbtuser -c "/usr/bin/qbittorrent-nox -d"" wikitext text/x-wiki rc.d/after.local:su - qbtuser -c "/usr/bin/qbittorrent-nox -d" 4221e8adb817dcc811c6be1a5c4cf832e9278d12 0 411 1912 1702 2015-12-04T10:38:58Z Pvdm 2 wikitext text/x-wiki This is how to stop a running service temporarily: systemctl stop servicename.service Send a kill: systemctl kill sshd.service systemctl kill -s HUP sshd.service This stops it from starting at boot, but does not stop a running service: systemctl disable servicename.service And there is one way to really really stop a service for good, short of uninstalling it, and that is masking it by linking it to /dev/null: ln -s /dev/null /etc/systemd/system/servicename.service systemctl daemon-reload When you do this you can't even start the service manually. Nothing can touch it. What if you change your mind? Pish tosh, it's easy. Simply delete the symlink and run systemctl enable servicename.service. While we're here, let's talk about two reload commands: daemon-reload and reload. The daemon-reload option reloads the entire systemd manager configuration without disrupting active services. reload reloads the configuration files for specific services without disrupting service, like this: systemctl reload servicename.service This reloads the actual configuration file used by the hardy sysadmin, for example the /etc/ssh/sshd_config file for an SSH server, and not its systemd unit file, sshd.service. So this is what to use when you make configuration changes. List active service units: systemctl --type=service list all service units: systemctl --type=service --all list systemd services: systemctl list-unit-files =default target= The system boots to '''default.target''' This is a symbolic link to '''multiuser.target''' or '''graphical.target'''. Changing the default runlevel/target is replacing the symbolic link ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target To change runlevel: systemctl isolate multi-user.target =booting= At boot time, on the kernel grub line, add: '''systemd.unit=xxxxx''' So what's taking so long? We can find out with the systemd-analyze blame command <pre>$ systemd-analyze blame 60057ms sendmail.service 51241ms firstboot-graphical.service 3574ms sshd-keygen.service 3439ms NetworkManager.service 3101ms udev-settle.service 3025ms netfs.service 2411ms iptables.service 2411ms ip6tables.service 2173ms abrtd.service 2149ms nfs-idmap.service 2116ms systemd-logind.service 2097ms avahi-daemon.service 1337ms iscsi.service</pre> If you like pretty graphs systemd includes a cool command for automatically generating an SVG image from the blame output, like this: systemd-analyze plot > graph1.svg To shutdown: systemctl poweroff =systemctl files= /lib/systemd/system/ /etc/systemd/system/ is for customized settings 5c962d99ba58180762f1b600ffe3b936f6c90565 0 490 1917 2016-01-28T15:55:54Z Pvdm 2 Created page with "het testen van een transistor is vrij eenvoudig: je zet je multimeter op het diode teken, daarna pak je de plus pool, rode draad van je multimeter en je zet deze op de basis..." wikitext text/x-wiki het testen van een transistor is vrij eenvoudig: je zet je multimeter op het diode teken, daarna pak je de plus pool, rode draad van je multimeter en je zet deze op de basis van de transistor, tussen basis en emitter en tussen basis en collector meet je nu de spanning van de PN overgang,(+-0.6v) draai de klemmen om en je mag geen spanning meten, tussen collector en emmitter mag je nooit spanning meten met + aan de basis heb je met een NPN te doen, met de min aan de basis heb je met een PNP te doen.... of nog makkelijker, neem er een waarvan je weet welke type het is en doe de bovenstaande test... als je weet dat je transistor goed is kan je de versterking meten door hem correct aan te sluiten aan de drie puntjes van je multimeter, je krijg normaal maar op 1 manier een correcte waarde.. 37b3c6d16976212d5351cefdc13aefb8a09f4c50 0 491 1935 1934 2016-04-08T12:28:53Z Pvdm 2 wikitext text/x-wiki <pre> name 1 2 3 4 samsie 4589 23s 52s 28s nieuwe 5188 20s 35s 25s lapx 5787 18s 39s 22s amd64 6030 34s 43s 43s ams251 6933 23s 59s 29s ams008 6200 27 78 34 1-first column in bogomips. 2-second is time in seconds from this command: time echo "scale=5000; a(1)*4" | bc -l 3-third is this command time $(i=0; while (( i < 9999999 )); do (( i ++ )); done) 4-fourth is this command: echo '2^2^22' | time bc > /dev/null </pre> 4c2a729b18fb2b2334aec195ab3ebd719a202e8f 0 492 1942 1941 2016-08-05T06:13:50Z Pvdm 2 wikitext text/x-wiki <pre> 1970 "A new generation of the series A80 professional studio tape recorders is introduced in the Spring of this year." * 1971 "A new studio tape recorder, the model A80/R "Broadcasting Version" complements the A80 series. * 1972 "The versatile concept of the professional studio recorder A80 permits its conversion into a quadraphonic model, which is called A80RT-Quadra." * 1975 Studer Canada launched the A80/VU-16-2" at WABE '75 Hotel Vancouver. Bruno Hochstrasser loaned it to Little Mountain Sound (LMS) Vancouver where I worked 1975 Studer Canada A80/VU price list shows "Mk I" 8T-1" and 16T-2" transportable versions 1977 LMS installed the first Studer A80/VU-24-2" Mk II in Western Canada; I worked on this project 1980s A80 Mk III and Mk IV multi-tracks with faster punch-in with a single erase head closer to record head, transformerless I/O, Dolby HX (Mk IV), etc 1989 A80 End of Production ** 1998 A80 End of Maintenance Support by audiohouse.ch GmbH ** </pre> I'm unable to find the changeover date from A80/VU Mk I to Mk II, estimate early to mid 1970s as technology and designs improved. Others in this forum might provide more details. I believe serial numbers starting from "10,000" were assigned to Mk II machines to distinguish them from Mk I. A80 VU Mark I has centre-tapped repro heads, black frame VU meters, no removable EQ cards for Rec/Sync/Repro cards as Mk II, etc. Re: A80 sales volume: "The fundamental corporate policy of Studer is to manufacture and market only well-engineered products with a long service life. With over 10,000 sales, the series A80 proves that Studer customers appreciate this policy." *** I'll add that a source of confusion is that the A80 was originally introduced as simply the A80, but was then later re-named the A80/VU. This was done to try to better differentiate it from the subsequently introduced, lower-cost A80/R and A80/RC versions that were developed for the broadcast market. As most readers here know, the A80/R and RC borrowed the earlier developed audio channel electronics from the B62. This was done to make the A80/R and RC versions available at lower cost. ae50ba2201a6c1a20d58455194f3c49b998f4aea 0 43 1945 120 2016-10-25T13:25:14Z Pvdm 2 wikitext text/x-wiki Today in IRC suseROCKS needed to find all duplicate files in a directory by their content, not by their file name, so we whipped up this fancy little 1 liner bash script to do the trick: find . -type f -exec md5sum '{}' \; | sort | awk 'dup[$1]++{print $2}' EDIT: As Andreas suggested, using xargs instead of -exec is much faster, here is the updated command: find . -type f -print0 | xargs -0 md5sum | sort | awk 'dup[$1]++{print $2}' 9b18707303d3f49735a11f80acf71841b17d77e7 0 493 1947 2016-10-26T09:27:49Z Pvdm 2 Created page with "pong: yes $COLUMNS $LINES|awk 'BEGIN{x=y=e=f=1}{if(x==$1||!x){e*=-1};if(y==$2||!y){f*=-1};x+=e;y+=f;printf "\033[%s;%sH",y,x;system("sleep .02")}'" wikitext text/x-wiki pong: yes $COLUMNS $LINES|awk 'BEGIN{x=y=e=f=1}{if(x==$1||!x){e*=-1};if(y==$2||!y){f*=-1};x+=e;y+=f;printf "\033[%s;%sH",y,x;system("sleep .02")}' c200ac938e23ec3dcd18440803aa3c811654ceef 0 494 1954 1953 2016-11-25T13:17:30Z Pvdm 2 wikitext text/x-wiki # topas # nmon export TERM=aixterm # df (-m) : megabytes # du -mx # du -sm * :grootte van subdirs in megabytes # du -sk ./* | sort -rn :sorteer huidige subdirs op grootte # lslv fslv04 :laat eigenschappen zien logical volume (typ in zonder /dev/) # lsvg -l ontrodat :laat filesystems zien in ontrodat # lsvg ontrodat :laat physical size zien # chfs -a size=(+)1G /fsnw/local :vergroot tot/met 1GB Om fysieke disk te vinden: # lsvg -p rhodat > hdisk6 # /net/beheer/script/get_disk_info > hdisk5 6000000000...0...000 800GB 2e veld is de LUN dit gebruiken voor aanvraag lunresize Als er een lun vergroot is, dan moet je AIX inlichten: # lspv hdisk6 # chvg -g rhodat : scan lun, check dan of grootte gewijzigd is # lsvg rhodat : check Nu filesysteem vergroten: # chfs -a size=+25G /ont/data/DBGA/oracle/rho # df -g 1825cfa7293779088bd98748148aa53ec691083e 10 496 1961 2017-02-09T07:49:49Z Pvdm 2 Created page with "Snapper is not restricted to creating and managing snapshots automatically by configuration; you can also create snapshot pairs ("before and after") or single snapshots manual..." wikitext text/x-wiki Snapper is not restricted to creating and managing snapshots automatically by configuration; you can also create snapshot pairs ("before and after") or single snapshots manually using either the command line tool or the YaST module. All Snapper operations are carried out for an existing configuration. You can only take snapshots of partitions or volumes for which a configuration exists. By default the system configuration (root) is used. If you want to create or manage snapshots for your own configuration you need to explicitly choose it. Use the Current Configuration drop-down box in YaST or specify the -c on the command line (snapper -c MYCONFIG COMMAND). 8c46287e61c7a01913bcd5c3711f0c5ca0e0173b 0 495 1964 1963 2017-02-09T07:52:41Z Pvdm 2 /* YaST Snapper GUI */ wikitext text/x-wiki ==Introduction== This article assumes you will be using Snapper with the Btrfs filesystem. During a fresh install of openSUSE, the default is to use Btrfs on root, meaning / and the filesystem XFS on /home. If you select the option to not seperate /home during openSUSE install, the default is for everything, including /home, to be under Btrfs. If you decide to use Btrfs & Snapper (default) during a fresh openSUSE install, it will automatically configure Snapper for you. This automatic configuration of Snapper means that snapshots will be made automatically when you use YaST2 and/or zypper. Please read section ''Software Requirements'' below for caveat. You may convert EXT3 & EXT4 filesystems to Btrfs to take advantage of Snapper. Using Snapper on EXT4 filesystem is ''highly'' discouraged. ==Important Details== The default behaviour when Snapper is configured to run on root, meaning /, is to '''''exclude''''' every Btrfs subvolume. This the same behaviour as on SUSE Enterprise. This means that if you have the subvolume /srv Snapper will not snapshot anything in /srv unless told specifically by you to do so. This also means that if you add a subvolume to / at any point in time, it will be excluded from Snapper's default snapshot behaviour. Always be root when using Snapper or YaST2, unless otherwise specified. YaST2 comes with a Snapper module called yast2-snapper and may be used to check and manipulate snapshots. It does not, however, have the ability to change Snapper configurations. That must be done in the terminal. Taking snapshots is automatically enabled if the root partition (/) is big enough (approximately more than 8GB). Please remember: taking snapshots on partitions other than / is not enabled by default. To see what subvolumes are created under / and therefore see which directories (subvolumes) are excluded from the default snapshots behaviour: # btrfs subvolume list / To have Snapper create a snapshot of a subvolume, you can either do it manually one-time via the snapper program, or create a new snapper config file. More information in the tutorial. ==Software Requirements== You always need this package: snapper If you use YaST2 to install, update or remove packages and want to have snapper automatically create snapshots when you use this tool: yast2-snapper If you use zypper to install, update or remove packages and want to have snapper automatically create snapshots when you use this tool: snapper-zypp-plugin If you want to have the ability for advanced btfs snapshot boot menu management: grub2-snapper-plugin '''WARNING''': the above packages are not always installed by default. What gets installed depends on what choices you make during the openSUSE installation process. Make sure you have the appropriate (usually that means all) packages listed above installed before making changes to your system, otherwise you may be in for a surprise when snapper does not automatically create snapshots you thought it would. ==Snapper Basic Usage== Snapper is not restricted to creating and managing snapshots automatically by configuration; you can also create snapshot pairs ("before and after") or single snapshots manually using either the command line tool or the YaST module. All Snapper operations are carried out for an existing configuration. You can only take snapshots of partitions or volumes for which a configuration exists. By default the system configuration (root) is used. If you want to create or manage snapshots for your own configuration you need to explicitly choose it. Use the Current Configuration drop-down box in YaST or specify the -c on the command line (snapper -c ''MYCONFIG'' ''COMMAND''). === List all snapshots for the default configuration (root) === snapper list or snapper ls === Show which files and directories have been changed between snapshots === For files/directories changed between snapshot 21 and 22: snapper status 21..22 You can also show what files and directories have been changed from snapshot 41 going back to 39: snapper status 41..39 The output consists of a string encoding the status followed by the filename. The characters of the status string are: # "+" means the file was created # "-" means the file was deleted # "c" means the content of the file has changed # "t" means the type of the file has changed (e.g. from regular file to directory) # "p" means the permissions are have changed # "u" means the user ownership has changed # "g" means the group ownership has changed # "x" means the extended attribute information has changed # "a" means the ACL information has changed # "." means no change === Show the diff (difference in actual files) between snapshots === For diff between snapshot 71 and 72: snapper diff 71..72 You can also use this command to show the difference between a specific file. For example to show the diff from snapshot 71 to 72 only for file /etc/zypp/zypp.conf you would do the following: snapper diff 71..72 /etc/zypp/zypp.conf === Cleanup Algorithms === Unless you have a good reason to do otherwise, you should always specify the cleanup algorithm when creating a snapshot, otherwise the snapshot will never be deleted unless you do it manually. You do this by adding the following to your snapper commands: --cleanup-algorithm <number|timeline|empty-pre-post> The following commands assume you will be creating snapshots on the default system configuration (root). As mentioned above, if you want to use the non-default configuration, add the following the the snapshot commands: -c ''MYCONFIG'' Create a snapshot of the type ''pre'' and prints the snapshot number. First command needed to create a pair of snapshots used to save a "before" and "after" state. snapper create --type pre --print-number --description "Before the Apache config cleanup" --cleanup-algorithm number Create a snapshot of the type ''post'' paired with the pre snapshot number 30. Second command needed to create a pair of snapshots used to save a "before" and "after" state. snapper create --type post--pre-number 30 --description "After the Apache config cleanup" --cleanup-algorithm number Creates a stand-alone snapshot (type single) for the default (root) configuration with a description. Because no cleanup-algorithm is specified, the snapshot will never be deleted automatically. snapper create --description "Snapshot for week 2 2014" === Deleting Snapshots === Delete snapshot 65 for the default (root) configuration: snapper delete 65 ==Snapper Tutorial== {{Info|'''The following tutorial assumes you have installed openSUSE using YaST (default installer) and selected Btrfs for your root and home file system. The default is to use Btrfs on root, but not on /home. If your /home is not using Btrfs, this tutorial still applies, just do not follow through with the directions when it comes to configuring or using Snapper on /home.'''}} First let us check how YaST has configured snapper: # snapper list-configs Config | Subvolume -------+---------- root | / As you can see YaST has created a snapper config called "root" for your root file system. You can see what snapshots exist: # snapper list Type | # | Pre # | Date | Cleanup | Description | Userdata -------+---+-------+------------------------------+----------+-------------+--------- single | 0 | | | | current | single | 1 | | Tue 22 Nov 2011 10:30:02 CET | timeline | timeline | Snapshot #0 always refers to the current system. There might already be several other snapshots depending on the uptime of your system and on whether you already used YaST or zypper. Now we want to try snapper as a undo tool for YaST. First we run YaST: # yast2 system_settings Within YaST enable the SysReq. After you have finished YaST you see two new snapshots: # snapper list Type | # | Pre # | Date | Cleanup | Description | Userdata -------+---+-------+------------------------------+----------+----------------------+--------- single | 0 | | | | current | single | 1 | | Tue 22 Nov 2011 10:30:02 CET | timeline | timeline | pre | 2 | | Tue 22 Nov 2011 10:41:28 CET | number | yast system_settings | post | 3 | 2 | Tue 22 Nov 2011 10:41:49 CET | number | | === Types of Snapshots === It's time to explain the type of snapshots. Snapper creates a snapshot before and after YaST runs, these snapshots are called pre and post respectively. The post snapshots knows which pre snapshots belongs to it. By having a pre and post snapshot we can see what changes happened to the file system while YaST was running. Single snapshots have no special relationship to other snapshots. === Seeing What Has Changed (YaST) === Using snapper, it is easy to see what has changed while YaST was running. To do so you have to pass the number of the pre and post snapshot: # snapper status 2..3 c... /etc/sysctl.conf The 'c' means that the content of the file has changed. We can also see the diff of the file: # snapper diff 2..3 --- /.snapshots/2/snapshot/etc/sysctl.conf 2011-11-22 10:35:43.355493753 +0100 +++ /.snapshots/3/snapshot/etc/sysctl.conf 2011-11-22 10:41:47.019512185 +0100 @@ -17,7 +17,7 @@ # See sysctl.conf(5) and sysctl(8) for more information # #### -kernel.sysrq = 0 +kernel.sysrq = 1 net.ipv4.ip_forward = 0 net.ipv4.tcp_syncookies = 1 net.ipv6.conf.all.forwarding = 0 So, if you don't like the change done by YaST and want to revert it call: # snapper undochange 2..3 create:0 modify:1 delete:0 undoing change... undoing change done But note that snapper does not tell the kernel about the change like YaST did so you must either do so yourself or reboot. === Adding /home To Snapper === During installation YaST does not setup a snapper config for /home. We can do so manually: # snapper -c home create-config /home Whenever you want to use snapper for /home you must provide the option -c home. Now you can see what files have changed since the last hourly snapshot: # snapper -c home list Type | # | Pre # | Date | Cleanup | Description | Userdata -------+---+-------+------------------------------+----------+-------------+--------- single | 0 | | | | current | single | 1 | | Tue 22 Nov 2011 11:30:01 CET | timeline | timeline | # snapper -c home status 1..0 comparing snapshots... done +... /home/tux/just-married.jpg The '+' sign means that the file is new. === Manually Creating A Snapshot === If you manually want to create a snapshot use: # snapper -c home create --description "before the big cleanup" == YaST Snapper GUI == Finally yast2-snapper provides a YaST UI for snapper. == Troubleshooting == === Logs === Snapper logs can be found in /var/log/snapper.log, check this file if you are having issues as it may contain useful troubleshooting information. ==Snapper Videos== [https://www.youtube.com/watch?v=GJgWvTLo07k Snapper Quick Overview (4min)] [https://www.youtube.com/v/9H7e6BcI5Fo?start=209 Greg Kroah-Hartman & SUSE Linux Enterprise Product Manager Demo Snapper (~7min)] [https://www.youtube.com/watch?v=86soSAZlYo8 Snapper, Btrfs & LVM Presentation (22min)] f113b8a77fbd5f92651833b3e0736a371f0e28c2 0 498 1973 1972 2017-04-17T13:35:47Z Pvdm 2 wikitext text/x-wiki Q. What is different about the varieties of Dolby noise reduction? By Hugh Robjohns I never did quite understand the subtle differences between all the different variants of Dolby — A, B, C, HX and SR. Could you explain them to me? Are there any others I've missed? What are Dolby Labs doing these days? I guess they've undergone some 'reduction' themselves... Technical Editor Hugh Robjohns replies: '''Dolby A''' was the first professional noise-reduction system — launched in 1967 if memory serves — and it used four separate frequency processing bands. You can think of them crudely as bass, mid-range, treble and high treble, with the top two overlapping so that the 'hiss region' was processed more heavily than the rest. Avoiding line-up errors between encoding and decoding was crucial, so the infamous Dolby warble tone was used to identify encoded tapes and to allow accurate replay alignment. Dolby A was originally used to get respectable audio performance out of early professional video recorders, but was later adopted for multitrack recording and cinema optical soundtracks. '''Dolby B''' was a very simple domestic system intended to improve the performance of compact cassette recorders. It was also used on some later domestic quarter-inch machines. Dolby B was a single-band system affecting only the high end, with very modest compansion. It had no facility, or indeed any practical need, for replay alignment. '''Dolby C''' was a much more aggressive multi-band version originally intended for small-format professional video-tape systems and narrow-gauge semi-professional studio multitrack recorders. It was very sensitive to mistracking, but was unfortunately designed without any line-up tone facility to calibrate playback levels. In the professional market, Dolby A was superseded by '''Dolby SR''', which was Dolby's most sophisticated multi-band noise reduction system. This employed 10 bands altogether, some operating at fixed frequencies and others moving automatically to suit the material, and allowed the user to achieve a signal-to-noise ratio of around 90dB from analogue tape. However, although it was a very clever and effective system it arrived just a few years too late and the digital revolution effectively eclipsed it. Dolby SR used a modulated noise signal for identification and replay alignment. Finally, '''Dolby S''' (one you missed off your list) was a last-ditch attempt aimed at semi-pro and domestic recorders, and was a halfway house between Dolby SR and Dolby C. It still had no built-in line-up facility, though. It was used on some semi-pro narrow-gauge multitrackers and the last of the high-end hi-fi cassette recorders. '''Dolby HX''' is not a noise-reduction system at all — it is a clever system to avoid over-biasing on analogue tape machines using high-output tapes. This system was used on some high-end domestic cassette recorders and the last of the professional analogue two-track machines, such as the Studer A807. Dolby HX is a once-only process that needs no decoding. In essence, it reduces the bias level if there is a lot of high-frequency content in the audio signal, thus preventing over-biasing and the noise artefacts and frequency-response errors that go with it. Dolby Labs still make Dolby SR and A systems for analogue multitrack and cinema applications, and I guess they are still collecting licensing revenues from the other systems when they are used on domestic cassette recorders and the like. However, most of the company's efforts these days are geared towards digital data-reduction systems, which are based entirely on the frequency-masking principles first exploited by Dolby's analogue noise-reduction systems. That is why Dolby AC3 has always been amongst the best of the data-reduction codecs for a given data rate — the company had a major head start on the rest of the field. 57877554be3dcde22ce8b157af4e6dd2d7c96881 0 405 1979 1966 2017-04-26T07:12:00Z Pvdm 2 wikitext text/x-wiki *list available devices btrfs device scan *list available filesystems btrfs filesystem show *create volume mkfs.btrfs /dev/sdX *'''stripe''' across devices (mirror metadata + stripe data) mkfs.btrfs /dev/sda /dev/sdb /dev/sdc *'''stripe''' across devices (stripe metadata + stripe data) mkfs.btrfs -m raid0 /dev/sda /dev/sdb /dev/sdc *'''mirror''' across devices (mirror metadata + mirror data) mkfs.btrfs -m raid10 -d raid10 /dev/sda /dev/sdb /dev/sdc *create subvolume btrfs subvolume create /mnt/nonsense where /mnt is the mountpoint of the btrfs volume *list subvolumes btrfs subvolume list /mnt *create snapshot mkdir /mnt/snapshots btrfs subvolume snapshot /mnt/nonsense /mnt/snapshots/vrijdag *add a new device btrfs device add /dev/sda8 /mnt *remove a device btrfs delete /dev/sdb /mnt *free space: btrfs fi df / *show snapshots snapper list *delete all snapshots for i in {1..20000}; do snapper delete $i; done 2015: *balance om ruimte vrij te maken: btrfs balance start /tmp/bla als geen ruimte vrij: btrfs balance start -musage=50 -dusage=50 /tmp/bla btrfs fi show /tmp/bla btrfs fi df /tmp/bla Onderhoud: btrfs scrub is used to scrub a btrfs filesystem, which will read all data and metadata blocks from all devices and verify checksums. Automatically repair corrupted blocks if there’s a correct copy available. btrfs scrub start -B /tmp/bla fstrim /tmp/bla for conventiaonal HD's: btrfs filesystem defragment /tmp/mnt/bla recursief een directory: btrfs filesystem defragment -r /tmp/mnt/bla 481b7f538b5077e7db648e181282d791e2a54e9d 0 500 1983 2017-05-01T19:00:56Z Pvdm 2 Created page with "Start a vm as non-root: # virsh -c qemu:///system start tumbleweed and view it: # virt-viewer -c qemu:///system tumbleweed" wikitext text/x-wiki Start a vm as non-root: # virsh -c qemu:///system start tumbleweed and view it: # virt-viewer -c qemu:///system tumbleweed f69256666d78404ca50fcfaa105aa50ac4b51633 0 502 1990 2017-06-06T19:16:45Z Pvdm 2 Created page with "Chris: “The RS-1700 was an update of the iconic RS-1500.” Comment: Just to nitpick, the 1700 was actually kind of an enhancement to the 1506. The RS-1500 and 1502 were ne..." wikitext text/x-wiki Chris: “The RS-1700 was an update of the iconic RS-1500.” Comment: Just to nitpick, the 1700 was actually kind of an enhancement to the 1506. The RS-1500 and 1502 were near-pro-grade 2-track machines that had a quarter-track play head over on the left side before the erase head. There was a switch on the headblock to control which play head hit the electronics. The machine only recorded in 2-track. The play-head switch was semi-reliable over time but can be cleaned and if it’s treated gently, the contacts just get dirty rather than fail like some 1960’s slide-switches. The RS-1520 was the 1500 with balanced inputs and outputs and bias and equalization trimmers. It was a professional grade 2-track tape recorder, certainly usable for broadcast production and lower-budget music production. The RS-1506 was a quarter-track version of the RS-1500, with a 2-track playback head over on the left above the quarter-track erase head. So then you get to the RS-1700. This was a consumer deck through and through, although a high end one. It was quarter-track (a consumer format) and bi-directions (in other words it would record both forward and reverse, no need to flip reels). It had the same motors and isolated-loop capstan system as the older machines. The heads were smaller and play and record heads were fit in one assembly (not one head like a typical cassette deck, separate heads in one can) so there was room for 6 heads in the same space as the 4 heads on the other decks. I don’t think this was a major compromise as far as performance, I think the 1700 spec’d out close or identical to the 1506. They are really nice decks, just understand they are high-end consumer decks, mainly because of the quarter-track format. Technics reel decks hold their own to this day. They are very gentle on old tapes, but the tension against the heads is low so they are non-ideal for edge-warped old tapes. They are dead-on speed accurate if the motor is working properly. There are electronic tweaks, but making sure all the capacitors are good would be my first repair. By the way, check out this website, showing the OTHER isolated-loop decks Panasonic sold in Japan: http://reeltoreelworld.blogspot.com/2009/02/doc-technics-adds.html The RS-1800 was sold outside of Japan. I’ve heard of some in the U.S. but never seen one. The little 7″ reel deck was only sold in Japan. Note the silver-faced 1700 in one ad. 5e85f012f6216c0b3727113594aed1d56fe13669 0 503 1994 1993 2017-06-15T12:37:57Z Pvdm 2 wikitext text/x-wiki Creating a bootable Windows 10 USB on linux 10 Aug 2016 - by 'Maurits van der Schee' Whenever I have to help somebody with Windows 10 I find myself making a bootable Windows 10 USB drive. If you are on Windows this is provided via a menu option, but on Ubuntu Linux this requires some commands. This post will explain in detail how to do this. =GPT partition table with FAT32 partition= Modern systems support UEFI booting and this differs from traditional BIOS in that it does not read the boot sector. Instead it will look in the /efi/ directory in a FAT32 partition of a drive with GPT partitioning. There are no partition flags (like 'boot') necessary either. =Getting the official Windows 10 ISO image= You can download the official Windows 10 ISO image from Microsoft by visiting: https://www.microsoft.com/en-us/software-download/windows10ISO But you must be on Linux (or pretend to be using user agent switcher) to download the file. =Writing to the USB drive= Your USB drive has a drive letter in Linux typically something like 'b', which leads to a path to the device of /dev/sdb and a partition path for the first partition of /dev/sdb1. To avoid you screwing up your computer I use 'h', which you should replace in the commands below. You can use the 'gparted' graphical tool to find the drive letter of your USB drive. If your USB drive is behaving weird, then you can reset it by issuing the following command: # dd if=/dev/zero of=/dev/sdh bs=512 count=1 Normally this is not nessecary. Then to create a new layout on the drive: # fdisk /dev/sdh This is what you should enter in fdisk: Press 'g' to create a new GPT, Press 'n' to create a new partition and accept the defaults, Press 't' to choose the partition type, Enter '11' for the 'Microsoft basic data' type. Press 'w' to write the changes to disk. The following command will format the first partition with FAT32. # mkdosfs -F32 /dev/sdh1 Now we need to mount the downloaded ISO file: # mount Downloads/Win10_1607_Dutch_x64.iso /mnt And copy all contents to the USB drive (this takes up to 15 minutes and shows no progress): # cp -R /mnt/* /media/maurits/39F5-8B34/ Now unmount the ISO... # umount /mnt and the USB drive before removing it: # umount /media/maurits/39F5-8B34/ To ensure the drive is OK, print the contents using 'fdisk': # fdisk /dev/sdh <pre> Welcome to fdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sdh: 7.2 GiB, 7735541760 bytes, 15108480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 1F574274-2552-4728-831F-90D768723297 Device Start End Sectors Size Type /dev/sdh1 2048 15108095 15106048 7.2G Microsoft basic data Command (m for help): q </pre> Note that the drive should say 'Disklabel type: gpt' and 'Microsoft basic data'. 1fd80cd117cc6d6233a0477a38e3975cd037d8a7 6 505 2006 2017-07-27T15:22:31Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 388 2016 1852 2017-07-31T13:14:23Z Pvdm 2 wikitext text/x-wiki <pre> sda1: swap sda2: / btrfs UUID=.....3858 sda3: /home xfs UUID=.....ce29 OLD: 1. systeem? 100mb ntfs (of 22gb?) 2. c: 230GB ntfs 3. d: 343GB ntfs 4. systeempartitie 22GB ntfs sda1 100MB ntfs system sda2 230GB ntfs c: mounted on /mnt/sda2 sda3 343GB extended partition sda4 22GB ntfs samsung recovery sda5 30GB ext4 / root partition sda6 2GB swap sda7 311GB fat32 /data </pre> [[File:samsie.png]] c731a17438834534c1f53a6375e59cd2cac8082b 0 487 2019 2018 2017-07-31T16:52:23Z Pvdm 2 /* How to make button for screen brightness work on your laptop in KDE */ wikitext text/x-wiki =How to make button for screen brightness work on your laptop in KDE= When I started using a newer kernel in openSUSE 13.2, I noticed the buttons for screen brightness were no longer functioning on my laptop. This is verry annoying, so I decided to do something about it. I am using KDE. I will try to write the instructions as generic as possible, so that it will hopefully work in your situation too. This is a HP ELitebook 8570p. ==find the right entry== First, we have to find the screen device, which is located somewhere in the /sys/devices/pci0000:00 directory. Somewhere in this directory is a file located with the name 'brightness'. Let's find it. So, as root: # find /sys/devices/pci0000:00 -name "brightness" /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness /sys/devices/pci0000:00/0000:00:1c.2/0000:24:00.1/leds/mmc0::/brightness /sys/devices/pci0000:00/0000:00:1c.3/0000:25:00.0/leds/phy0-led/brightness Remember, your output is probably different from what I got here. I have a radeon card, so the first line contains the device we will be working with. When you read the content of the 'file', you get the current brightness level: # cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness 235 The value lies somewhere between 0 and 255, it's a one byte value. You can test if this work for you by writing (still as root) a different value to that file: (remember to substitute the file for your graphics card) # echo 200 > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness If this works, you should see the brightness change, and you can go to the next step. edit: for samsung rv720: "echo 8 > /sys/class/backlight/samsung/brightness" to restore the brightness. edit2: newer kernel uses this: echo 100 > /sys/class/backlight/nv_backlight/brightness ==create the scripts== I created a simple QAD(quick and Dirty) 3 line script to read that value and increase it. I put the script in my home user's bin directory: user> vi ~/bin/brp <pre> br=$(cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness) br=$((br+10)) echo $br > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness </pre> I called it 'brp' which is nice and short and stands for ''''br'''ightness '''p'''lus' Note that I increase the value by 10 otherwise it would not change enough. You can vary that value of course to get finer control or get faster adjustment. I created a similar script called brm which decreases the value: user> vi ~/bin/brm And paste the content <pre> br=$(cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness) br=$((br-10)) echo $br > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness </pre> # chmod +x brm brp Now, the problem is that this file '''/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness''' may only be written by root. Notice that all commands manipulating the file so far have been executed as root. But you should have created the 2 script files brp and brm as your normal user account. To make the file world writeable: # chmod 777 /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness This will make the 2 scripts which are executed as your useraccount able to write to this file. ==configure KDE== Then, lastly, redefine the keys on your laptop for screen brightness to point to your script: * go to KDE - configure desktop * shortcuts and gestures * custom shortcuts * edit - new - global shortcut - command/URL * name: br-down * tab trigger: Shortcut - click on 'None' * press the brightness down key on your keyboard. It should appear in the button. * tab action: browse and point to your brm file (/home/$user/bin/brm) * click apply Repeat this for the brightness up script file, so you end up with 2 shortcuts. And that's it. This should work. Happy screening! ==configure crontab== Oh, and after a reboot, the chmod 777 of the brightness file is needed again. So I did a dirty hack and added this to my crontab: <pre> */3 * * * * root chmod 777 /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1/radeon_bl0/brightness </pre> 25d2fdf0c75f4e5eff3a2aa034b6fb4654ee426c 0 508 2021 2020 2017-07-31T17:02:15Z Pvdm 2 wikitext text/x-wiki <div style="margin-left:0cm;margin-right:0cm;"><span style="color:#000000;">Published on&nbsp;</span><span style="color:#000000;">Linux.com | The source for Linux information</span><span style="color:#000000;">&nbsp;(</span>[https://www.linux.com/ https://www.linux.com]<span style="color:#000000;">)</span></div> <div style="margin-left:0cm;margin-right:0cm;">[https://www.linux.com/ Home]<span style="color:#000000;">&nbsp;> How to Rescue a Non-booting GRUB 2 on Linux</span></div> == [https://www.linux.com/learn/how-rescue-non-booting-grub-2-Linux How to Rescue a Non-booting GRUB 2 on Linux]<span style="color:#000000;"> [1]</span> == <span style="color:#000000;">Submitted by&nbsp;</span>[https://www.linux.com/users/cschroder cschroder]<span style="color:#000000;">&nbsp;[2]&nbsp;on&nbsp;</span> <div style="color:#000000;">[[Image:Afbeelding2.png|top|alt="grub command shell"]]</div> <div style="color:#000000;">Once upon a time we had legacy GRUB, the Grand Unified Linux Bootloader version 0.97. Legacy GRUB had many virtues, but it became old and its developers did yearn for more functionality, and thus did GRUB 2 come into the world.</div> <span style="color:#000000;">GRUB 2 is a major rewrite with several significant differences. It boots removable media, and can be configured with an option to enter your system BIOS. It's more complicated to configure with all kinds of scripts to wade through, and instead of having a nice fairly simple&nbsp;</span><span style="color:#000000;">/boot/grub/menu.lst</span><span style="color:#000000;">&nbsp;file with all configurations in one place, the default is&nbsp;</span><span style="color:#000000;">/boot/grub/grub.cfg</span><span style="color:#000000;">. Which you don't edit directly, oh no, for this is not for mere humans to touch, but only other scripts. We lowly humans may edit&nbsp;</span><span style="color:#000000;">/etc/default/grub</span><span style="color:#000000;">, which controls mainly the appearance of the GRUB menu. We may also edit the scripts in&nbsp;</span><span style="color:#000000;">/etc/grub.d/</span><span style="color:#000000;">. These are the scripts that boot your operating systems, control external applications such as&nbsp;</span><span style="color:#000000;">memtest</span><span style="color:#000000;">&nbsp;and&nbsp;</span><span style="color:#000000;">os_prober</span><span style="color:#000000;">, and theming.</span><span style="color:#000000;">/boot/grub/grub.cfg</span><span style="color:#000000;">&nbsp;is built from&nbsp;</span><span style="color:#000000;">/etc/default/grub</span><span style="color:#000000;">&nbsp;and&nbsp;</span><span style="color:#000000;">/etc/grub.d/*</span><span style="color:#000000;">&nbsp;when you run the&nbsp;</span><span style="color:#000000;">update-grub</span><span style="color:#000000;">&nbsp;command, which you must run every time you make changes.</span> <span style="color:#000000;">The good news is that the&nbsp;</span><span style="color:#000000;">update-grub</span><span style="color:#000000;">&nbsp;script is reliable for finding kernels, boot files, and adding all operating systems to your GRUB boot menu, so you don't have to do it manually.</span> <span style="color:#000000;">We're going to learn how to fix two of the more common failures. When you boot up your system and it stops at the&nbsp;</span><span style="color:#000000;">grub></span><span style="color:#000000;">&nbsp;prompt, that is the full GRUB 2 command shell. That means GRUB 2 started normally and loaded the&nbsp;</span><span style="color:#000000;">normal.mod</span><span style="color:#000000;">&nbsp;module (and other modules which are located in&nbsp;</span><span style="color:#000000;">/boot/grub/[arch]/</span><span style="color:#000000;">), but it didn't find your&nbsp;</span><span style="color:#000000;">grub.cfg</span><span style="color:#000000;">&nbsp;file. If you see&nbsp;</span><span style="color:#000000;">grub rescue></span><span style="color:#000000;">&nbsp;that means it couldn't find&nbsp;</span><span style="color:#000000;">normal.mod</span><span style="color:#000000;">, so it probably couldn't find any of your boot files.</span> <div style="color:#000000;">How does this happen? The kernel might have changed drive assignments or you moved your hard drives, you changed some partitions, or installed a new operating system and moved things around. In these scenarios your boot files are still there, but GRUB can't find them. So you can look for your boot files at the GRUB prompt, set their locations, and then boot your system and fix your GRUB configuration.</div> === GRUB 2 Command Shell === <div style="color:#000000;">The GRUB 2 command shell is just as powerful as the shell in legacy GRUB. You can use it to discover boot images, kernels, and root filesystems. In fact, it gives you complete access to all filesystems on the local machine regardless of permissions or other protections. Which some might consider a security hole, but you know the old Unix dictum: whoever has physical access to the machine owns it.</div> <span style="color:#000000;">When you're at the&nbsp;</span><span style="color:#000000;">grub></span><span style="color:#000000;">&nbsp;prompt, you have a lot of functionality similar to any command shell such as history and tab-completion. The&nbsp;</span><span style="color:#000000;">grub rescue></span><span style="color:#000000;">&nbsp;mode is more limited, with no history and no tab-completion.</span> <span style="color:#000000;">If you are practicing on a functioning system, press C when your GRUB boot menu appears to open the GRUB command shell. You can stop the bootup countdown by scrolling up and down your menu entries with the arrow keys. It is safe to experiment at the GRUB command line because nothing you do there is permanent. If you are already staring at the&nbsp;</span><span style="color:#000000;">grub></span><span style="color:#000000;">&nbsp;or&nbsp;</span><span style="color:#000000;">grub rescue></span><span style="color:#000000;">prompt then you're ready to rock.</span> <span style="color:#000000;">The next few commands work with both&nbsp;</span><span style="color:#000000;">grub></span><span style="color:#000000;">&nbsp;and&nbsp;</span><span style="color:#000000;">grub rescue></span><span style="color:#000000;">. The first command you should run invokes the pager, for paging long command outputs:</span> <div style="color:#000000;">grub> set pager=1</div> <span style="color:#000000;">There must be no spaces on either side of the equals sign. Now let's do a little exploring. Type&nbsp;</span><span style="color:#000000;">ls</span><span style="color:#000000;">&nbsp;to list all partitions that GRUB sees:</span> <div style="color:#000000;">grub> ls</div> <div style="color:#000000;">(hd0) (hd0,msdos2) (hd0,msdos1)</div> <span style="color:#000000;">What's all this&nbsp;</span><span style="color:#000000;">msdos stuff</span><span style="color:#000000;">? That means this system has the old-style MS-DOS partition table, rather than the shiny new Globally Unique Identifiers partition table (GPT). (See&nbsp;</span>[https://www.linux.com/learn/tutorials/730440-using-the-new-guid-partition-table-in-linux-good-bye-ancient-mbr- Using the New GUID Partition Table in Linux (Goodbye Ancient MBR)]<span style="color:#000000;">&nbsp;[3]. If you're running GPT it will say&nbsp;</span><span style="color:#000000;">(hd0,gpt1)</span><span style="color:#000000;">. Now let's snoop. Use the&nbsp;</span><span style="color:#000000;">ls</span><span style="color:#000000;">&nbsp;command to see what files are on your system:</span> <div style="color:#000000;">grub> ls (hd0,1)/</div> <div style="color:#000000;">lost+found/ bin/ boot/ cdrom/ dev/ etc/ home/ lib/</div> <div style="color:#000000;">lib64/ media/ mnt/ opt/ proc/ root/ run/ sbin/ </div> <div style="color:#000000;">srv/ sys/ tmp/ usr/ var/ vmlinuz vmlinuz.old </div> <div style="color:#000000;">initrd.img initrd.img.old</div> <span style="color:#000000;">Hurrah, we have found the root filesystem. You can omit the&nbsp;</span><span style="color:#000000;">msdos</span><span style="color:#000000;">&nbsp;and&nbsp;</span><span style="color:#000000;">gpt</span><span style="color:#000000;">&nbsp;labels. If you leave off the slash it will print information about the partition. You can read any file on the system with the&nbsp;</span><span style="color:#000000;">cat</span><span style="color:#000000;">&nbsp;command:</span> <div style="color:#000000;">grub> cat (hd0,1)/etc/issue</div> <div style="color:#000000;">Ubuntu 14.04 LTS \n \l</div> <span style="color:#000000;">Reading&nbsp;</span><span style="color:#000000;">/etc/issue</span><span style="color:#000000;">&nbsp;could be useful on a multi-boot system for identifying your various Linuxes.</span> === Booting From grub> === <span style="color:#000000;">This is how to set the boot files and boot the system from the&nbsp;</span><span style="color:#000000;">grub></span><span style="color:#000000;">&nbsp;prompt. We know from running the&nbsp;</span><span style="color:#000000;">ls</span><span style="color:#000000;">&nbsp;command that there is a Linux root filesystem on&nbsp;</span><span style="color:#000000;">(hd0,1)</span><span style="color:#000000;">, and you can keep searching until you verify where&nbsp;</span><span style="color:#000000;">/boot/grub</span><span style="color:#000000;">&nbsp;is. Then run these commands, using your own root partition, kernel, and initrd image:</span> <div style="color:#000000;">grub> set root=(hd0,1)</div> <div style="color:#000000;">grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1</div> <div style="color:#000000;">grub> initrd /boot/initrd.img-3.13.0-29-generic</div> <div style="color:#000000;">grub> boot</div> <span style="color:#000000;">The first line sets the partition that the root filesystem is on. The second line tells GRUB the location of the kernel you want to use. Start typing&nbsp;</span><span style="color:#000000;">/boot/vmli</span><span style="color:#000000;">, and then use tab-completion to fill in the rest. Type&nbsp;</span><span style="color:#000000;">root=/dev/sd</span><span style="color:#000000;">''X''</span><span style="color:#000000;">&nbsp;to set the location of the root filesystem. Yes, this seems redundant, but if you leave this out you'll get a kernel panic. How do you know the correct partition? hd0,1 = /dev/sda1. hd1,1 = /dev/sdb1. hd3,2 = /dev/sdd2. I think you can extrapolate the rest.</span> <span style="color:#000000;">The third line sets the&nbsp;</span><span style="color:#000000;">initrd</span><span style="color:#000000;">&nbsp;file, which must be the same version number as the kernel.</span> <div style="color:#000000;">The fourth line boots your system.</div> <div style="color:#000000;">On some Linux systems the current kernels and initrds are symlinked into the top level of the root filesystem:</div> <div style="color:#000000;">$ ls -l /</div> <div style="color:#000000;">vmlinuz -> boot/vmlinuz-3.13.0-29-generic</div> <div style="color:#000000;">initrd.img -> boot/initrd.img-3.13.0-29-generic</div> <span style="color:#000000;">So you could boot from&nbsp;</span><span style="color:#000000;">grub></span><span style="color:#000000;">&nbsp;like this:</span> <div style="color:#000000;">grub> set root=(hd0,1)</div> <div style="color:#000000;">grub> linux /vmlinuz root=/dev/sda1</div> <div style="color:#000000;">grub> initrd /initrd.img</div> <div style="color:#000000;">grub> boot</div> === Booting From grub-rescue> === <span style="color:#000000;">If you're in the GRUB rescue shell the commands are different, and you have to load the&nbsp;</span><span style="color:#000000;">normal.mod&nbsp;</span><span style="color:#000000;">and</span><span style="color:#000000;">linux.mod&nbsp;</span><span style="color:#000000;">modules:</span> <div style="color:#000000;">grub rescue> set prefix=(hd0,1)/boot/grub</div> <div style="color:#000000;">grub rescue> set root=(hd0,1)</div> <div style="color:#000000;">grub rescue> insmod normal</div> <div style="color:#000000;">grub rescue> normal</div> <div style="color:#000000;">grub rescue> insmod linux</div> <div style="color:#000000;">grub rescue> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1</div> <div style="color:#000000;">grub rescue> initrd /boot/initrd.img-3.13.0-29-generic</div> <div style="color:#000000;">grub rescue> boot</div> <div style="color:#000000;">Tab-completion should start working after you load both modules.</div> === Making Permanent Repairs === <div style="color:#000000;">When you have successfully booted your system, run these commands to fix GRUB permanently:</div> <div style="color:#000000;"><nowiki># update-grub</nowiki></div> <div style="color:#000000;">Generating grub configuration file ...</div> <div style="color:#000000;">Found background: /usr/share/images/grub/Apollo_17_The_Last_Moon_Shot_Edit1.tga</div> <div style="color:#000000;">Found background image: /usr/share/images/grub/Apollo_17_The_Last_Moon_Shot_Edit1.tga</div> <div style="color:#000000;">Found linux image: /boot/vmlinuz-3.13.0-29-generic</div> <div style="color:#000000;">Found initrd image: /boot/initrd.img-3.13.0-29-generic</div> <div style="color:#000000;">Found linux image: /boot/vmlinuz-3.13.0-27-generic</div> <div style="color:#000000;">Found initrd image: /boot/initrd.img-3.13.0-27-generic</div> <div style="color:#000000;">Found linux image: /boot/vmlinuz-3.13.0-24-generic</div> <div style="color:#000000;">Found initrd image: /boot/initrd.img-3.13.0-24-generic</div> <div style="color:#000000;">Found memtest86+ image: /boot/memtest86+.elf</div> <div style="color:#000000;">Found memtest86+ image: /boot/memtest86+.bin</div> <div style="color:#000000;">done</div> <div style="color:#000000;"><nowiki># grub-install /dev/sda</nowiki></div> <div style="color:#000000;">Installing for i386-pc platform.</div> <div style="color:#000000;">Installation finished. No error reported.</div> <span style="color:#000000;">When you run&nbsp;</span><span style="color:#000000;">grub-install</span><span style="color:#000000;">&nbsp;remember you're installing it to the boot sector of your hard drive and not to a partition, so do not use a partition number like&nbsp;</span><span style="color:#000000;">/dev/sda1</span><span style="color:#000000;">.</span> === But It Still Doesn't Work === <span style="color:#000000;">If your system is so messed up that none of this works, try the&nbsp;</span>[http://www.supergrubdisk.org/ Super GRUB2 live rescue disk]<span style="color:#000000;">&nbsp;[4]. The official&nbsp;</span>[https://www.gnu.org/software/grub/manual/grub.html GNU GRUB Manual 2.00]<span style="color:#000000;">&nbsp;[5]&nbsp;should also be helpful.</span> <div style="color:#000000;">'''Tutorial Category:&nbsp;'''</div> [https://www.linux.com/tutorials/category/tutorials Tutorials]<span style="color:#000000;">&nbsp;[6]</span> <div style="margin-left:0cm;margin-right:0cm;"><span style="color:#000000;">Source URL:</span><span style="color:#000000;">&nbsp;</span>[https://www.linux.com/learn/how-rescue-non-booting-grub-2-Linux https://www.linux.com/learn/how-rescue-non-booting-grub-2-Linux]</div> <div style="margin-left:0cm;margin-right:0cm;"><span style="color:#000000;">Links:</span><span style="color:#000000;">[1] https://www.linux.com/learn/how-rescue-non-booting-grub-2-Linux</span><span style="color:#000000;">[2] https://www.linux.com/users/cschroder[3] https://www.linux.com/learn/tutorials/730440-using-the-new-guid-partition-table-in-linux-good-bye-ancient-mbr-[4] http://www.supergrubdisk.org/[5] https://www.gnu.org/software/grub/manual/grub.html[6] https://www.linux.com/tutorials/category/tutorials</span></div> 60b3b6a0de3ed2460d0b26f1aacb704f548d186f 0 509 2024 2023 2017-08-01T19:27:13Z Pvdm 2 wikitext text/x-wiki <pre> tumbleweed:~ # fdisk -l /dev/sda Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000c3032 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 4208639 4206592 2G 82 Linux swap / Solaris /dev/sda2 * 4208640 109064893 104856254 50G 83 Linux /dev/sda3 827269120 976773119 149504000 71.3G f W95 Ext'd (LBA) /dev/sda4 211466240 827269119 615802880 293.7G 83 Linux /data xfs /dev/sda5 827271168 913856511 86585344 41.3G 83 Linux / (tumbleweed, btrfs) /dev/sda6 913858560 976752639 62894080 30G 83 Linux /home (tumbleweed, xfs) Partition table entries are not in disk order. </pre> d074d14129f5b330eae67cd87bf9564cfb80e1c7 0 484 2025 1887 2017-08-02T06:18:15Z Pvdm 2 wikitext text/x-wiki To enable the (powered down) bluetooth adapter on openSUSE 13.2: rfkill unblock bluetooth = blueproximity = tweaking your settings should do the trick. Actually that's why I implemented a kind of testing mode. Open the preferences. Move to the second tab. The last control on that page "Measured atm (at the moment) shows the measured state. You can click on "Reset min/max" and leave the window open. If the window is open BlueProximity enters the simulation state which will not execute the action commands. It still measures the distances (on contrary to the pause mode which will completely disconnect the phone) and shows them at that control. Please note the text below the bar, which states "min" and "max" values - those are the min/max values of the measured distances after you pressed the Reset button last time. This information should give you a hint which values are to expect while you normally work in front of your computer. Remember to use all "poses" you normally use while using your computer. You should stay in those poses for at least 10 seconds so that the rssi value regulates on the new situation. That should give you realistic values for the locking distance. Use a value of at least 2 above the measured value and see if that already gives a secure setting for the distance. Also set the unlock distance to a value at least 2 smaller than the lock distance. Normally half of the lock distance gives a good result. You should play with the timer settings too. Don't put your lock timer to a value less than 5, at this moment my values are lock dist=7,dur=10. That is because I found out that sometimes unexpected com problems seem to exist between my phone and my pc - the rssi value drops to an unreasonable 8 but only for 5 seconds, it comes back to normal then which will never result in a value above 6 for longer than 10 seconds. My unlock time is also not set to 0 but to 2, the distance to 4. That way if I come back to my pc, the first of the two seconds below 5 is usually already passed and it takes about a second for me to sit down and once I sit down it unlocks almost immediately. This should also fix the screensaver problem as there is no immediate unlock possible. Please do note that using a fade out time for you screensaver, it should be set at least one second below the unlock timer so that the unlocking is never done while the locking is still in progress. It once rendered my whole desktop faded to grey which was eyefriendly for that time of the day but it wouldn't help in the office :-) The battery drain should be unnotable to phones that already had bluetooth activated. The explicit energy drain for an open bluetooth connection is specified to be 1 mW, my nokia has a 700mAh battery so it is ridiculously low in comparison :-) In other words, if you have bluetooth activated already you should not notice any difference at all. And btw, the visibility setting in your phone also has no effect on the battery too. Even though you would need to activate it only once to find your phone. After the mac address is entered you can switch your phone back to invisible if you like. This raises your phone's security a little bit. Hopefully this helps, 66cb5b9751690efb64316dff74dc9d84be50e172 0 21 2028 1888 2017-08-11T12:41:18Z Pvdm 2 wikitext text/x-wiki <pre> 82.95.225.202 PvdM 83.119.154.28 c.s 85.150.196.180 betert ---- linux fmt 0010322941R engeland (4802139149 op 1-12-2010) linux mag 194754204754 duits cchip DG7R0Y5 ---- siephi a t g m a i l soepsoep ---- cbond consu l culia p 1902jp en nog een x ==== xs voip werkgever 1 exclam ==== pas aarde 11882 Js8#gfC ===== xenpvdmattenC1tr1x01 ====== tqhjwc 500142 a ke we oggiz 10170391 ======== nl postnl mijn pakket p 0 stp @ kk 3 tj 3 ======== nav systeem. AK7HQ D2BAW appl 9.844.634510.500 besturingssyteem 628172 NFA2.0-KZ5, 28-01-2011 128 MB ram gps v1.20 boot 55.7716 kaart europa v855.2885 renault.multimedia.com ============== 337 419 739 kijker groep 56cdb5d319a231c90404202d016cb8f36e2d469c 0 510 2034 2017-09-06T06:22:00Z Pvdm 2 Created page with "BIOS: when keyboardlight comes on, press and hold F2" wikitext text/x-wiki BIOS: when keyboardlight comes on, press and hold F2 c9d632da12798867cd31b42cceb2a333eb1bc6df 0 511 2036 2017-09-06T06:27:40Z Pvdm 2 Created page with "==partitions== <pre> sda1: 450mb recovery sda2: 99mb sda3: 100bytes erg kleinpartitietije sda4: 50GB C: ----- sda5: 2G..." wikitext text/x-wiki ==partitions== <pre> sda1: 450mb recovery sda2: 99mb sda3: 100bytes erg kleinpartitietije sda4: 50GB C: ----- sda5: 2GB swap sda6: 27GB / sda7: 40GB /home </pre> ==hdparm== <pre> tecra:~ # hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: TOSHIBA THNSNK128GVN8 Serial Number: 17CS14H7T8GT Firmware Revision: K8TA4101 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Supported: 10 9 8 7 6 5 Likely used: 10 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 250069680 LBA48 user addressable sectors: 250069680 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 122104 MBytes device size with M = 1000*1000: 128035 MBytes (128 GB) cache/buffer size = unknown Form Factor: unknown (0x0007] Nominal Media Rotation Rate: Solid State Device Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Advanced power management level: 128 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE * Advanced Power Management feature set SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters * READ_LOG_DMA_EXT equivalent to READ_LOG_EXT * DMA Setup Auto-Activate optimization * Device-initiated interface power management * Software settings preservation Device Sleep (DEVSLP) * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) * reserved 69[3] * DOWNLOAD MICROCODE DMA command * SET MAX SETPASSWORD/UNLOCK DMA commands * WRITE BUFFER DMA command * READ BUFFER DMA command * DEVICE CONFIGURATION SET/IDENTIFY DMA commands * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 500080d9109a2088 NAA : 5 IEEE OUI : 00080d Unique ID : 9109a2088 Device Sleep: DEVSLP Exit Timeout (DETO): 50 ms (drive) Minimum DEVSLP Assertion Time (MDAT): 10 ms (drive) Checksum: correct </pre> 00b3a75f41d4f8fade607ae011a1d5390ad98d49 0 512 2038 2017-09-07T12:10:20Z Pvdm 2 Created page with "tecra z50-c-14t" wikitext text/x-wiki tecra z50-c-14t 543c7ff3f9c9b9b98a753057819c3d0b1bbaeece 0 515 2058 2050 2017-09-27T08:39:25Z Pvdm 2 wikitext text/x-wiki # for d in /dev/video* ; do echo $d ; v4l2-ctl --device=$d -D --list-formats ; echo '==============='; done # v4l-info /dev/video0 fcf05ba8e5a3bcfe3cd0a6b48021406b1e2d5b3d 0 518 2062 2017-09-27T08:50:33Z Pvdm 2 Created page with "<pre> pvdm@amd64:zm > v4l-info /dev/video2 ### v4l2 device info [/dev/video2] ### general info VIDIOC_QUERYCAP driver : "pac207" card..." wikitext text/x-wiki <pre> pvdm@amd64:zm > v4l-info /dev/video2 ### v4l2 device info [/dev/video2] ### general info VIDIOC_QUERYCAP driver : "pac207" card : "CIF Single Chip " bus_info : "usb-0000:00:10.1-2.4" version : 4.4.87 capabilities : 0x85200001 [VIDEO_CAPTURE,?,READWRITE,STREAMING,(null)] standards inputs VIDIOC_ENUMINPUT(0) index : 0 name : "pac207" type : CAMERA audioset : 0 tuner : 0 std : 0x0 [] status : 0x0 [] video capture VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE) index : 0 type : VIDEO_CAPTURE flags : 1 description : "GSPCA PAC207" pixelformat : 0x37303250 [P207] VIDIOC_G_FMT(VIDEO_CAPTURE) type : VIDEO_CAPTURE fmt.pix.width : 352 fmt.pix.height : 288 fmt.pix.pixelformat : 0x37303250 [P207] fmt.pix.field : NONE fmt.pix.bytesperline : 352 fmt.pix.sizeimage : 101952 fmt.pix.colorspace : SRGB fmt.pix.priv : 4276996862 </pre> 8d59974f18e519814743839cc44bec44c107b6e8 0 520 2070 2017-10-02T07:07:47Z Pvdm 2 Created page with "<pre> Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Users\pvdm>ipconfig /all Windows IP Configuration Host Name . . . ...." wikitext text/x-wiki <pre> Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Users\pvdm>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : DESKTOP-VLNQI5M Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : hotspots Ethernet adapter Ethernet: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Ethernet Connection I219-V Physical Address. . . . . . . . . : EC-21-E5-A9-CE-27 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 1: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : 14-AB-C5-3D-7B-C0 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Wi-Fi: Connection-specific DNS Suffix . : hotspots Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8260 Physical Address. . . . . . . . . : 14-AB-C5-3D-7B-BF DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::9daa:b314:5819:3350%9(Preferred) IPv4 Address. . . . . . . . . . . : 100.123.5.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.240.0 Lease Obtained. . . . . . . . . . : Monday, 2 October 2017 08:57:30 Lease Expires . . . . . . . . . . : Monday, 2 October 2017 09:02:29 Default Gateway . . . . . . . . . : 100.123.0.1 DHCP Server . . . . . . . . . . . : 100.123.0.1 DHCPv6 IAID . . . . . . . . . . . : 51686341 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-40-50-0F-EC-21-E5-A9-CE-27 DNS Servers . . . . . . . . . . . : 194.109.218.174 194.109.218.175 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 14-AB-C5-3D-7B-C3 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\pvdm> f4985eb02abc6eadbf8374eb3918053d633776a9 0 514 2071 2048 2017-10-05T11:46:22Z Pvdm 2 wikitext text/x-wiki <pre>=============== /dev/video1 Driver Info (not using libv4l2): Driver name : gspca_zc3xx Card type : USB Camera (041e:401f) Bus info : usb-0000:00:10.1-2.1 Driver version: 4.4.87 Capabilities : 0x85200001 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x05200001 Video Capture Read/Write Streaming Extended Pix Format ioctl: VIDIOC_ENUM_FMT Index : 0 Type : Video Capture Pixel Format: 'JPEG' (compressed) Name : JFIF JPEG =============== Zoneminder: PAL,auto, 24bit color, 320x240 fd547df42d8bfff44c9f8adf9e5d290bda242eba 0 517 2072 2060 2017-10-05T11:51:43Z Pvdm 2 wikitext text/x-wiki <pre> pvdm@amd64:zm > v4l-info /dev/video0 ### v4l2 device info [/dev/video0] ### general info VIDIOC_QUERYCAP driver : "pwc" card : "Logitech QuickCam Zoom" bus_info : "usb-0000:00:10.1-2.2" version : 4.4.87 capabilities : 0x85200001 [VIDEO_CAPTURE,?,READWRITE,STREAMING,(null)] standards inputs VIDIOC_ENUMINPUT(0) index : 0 name : "Camera" type : CAMERA audioset : 0 tuner : 0 std : 0x0 [] status : 0x0 [] video capture VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE) index : 0 type : VIDEO_CAPTURE flags : 1 description : "Raw Philips Webcam Type (New)" pixelformat : 0x32435750 [PWC2] VIDIOC_ENUM_FMT(1,VIDEO_CAPTURE) index : 1 type : VIDEO_CAPTURE flags : 0 description : "Planar YUV 4:2:0" pixelformat : 0x32315559 [YU12] VIDIOC_G_FMT(VIDEO_CAPTURE) type : VIDEO_CAPTURE fmt.pix.width : 160 fmt.pix.height : 120 fmt.pix.pixelformat : 0x32315559 [YU12] fmt.pix.field : NONE fmt.pix.bytesperline : 160 fmt.pix.sizeimage : 28800 fmt.pix.colorspace : SRGB fmt.pix.priv : 4276996862 </pre> Zoneminder PAL M, YUV420, 24bit color, 320x240 e45aef26465899e9082111da76f76e688b023921 0 519 2076 2064 2017-10-16T06:36:52Z Pvdm 2 wikitext text/x-wiki *[[Philips Webcam]] *[[Logitech quickcam]] *[[creative cylinder webcam]] *[[p2pwificam]] *[[HC-608]] *[[gspca]] ecb4768cdf018b1755f49a917be202abfa857b24 0 521 2080 2079 2017-10-17T19:27:53Z Pvdm 2 wikitext text/x-wiki Dit is de 2e webcam. rtsp://192.168.1.34/iphone/11?admin:pw& werkt goed in vlc <pre>SOURCE: RTSP RTP/RTSP 192.168.1.34 554 /iphone/11?admin:PASSWD& 24bit 1280 720 use rtsp responce media url v CONTROL: controllable v ONVIF Camera usr=admin&pwd=PASSWD 192.168.1.34:8080 hieronder geen idee? http://192.168.1.34/cgi-bin/view.cgi?chn=1&u=admin&p=password deze ook 8af9fc9180e06003faf6d325c75854552e07b288 0 523 2092 2017-11-01T10:22:16Z Pvdm 2 Created page with "CPU Chipset Geheugen Grafische Ondersteuning Multi-GPU Uitbreidingsslots Opslag LAN Audio AMD Socket FM2 Athlon™/A- Series Processors Supports CPU up to 4 cores Supports AMD..." wikitext text/x-wiki CPU Chipset Geheugen Grafische Ondersteuning Multi-GPU Uitbreidingsslots Opslag LAN Audio AMD Socket FM2 Athlon™/A- Series Processors Supports CPU up to 4 cores Supports AMD® Turbo Core 3.0 Technology AMD A85X FCH(Hudson D4) 4 x DIMM, Max. 64GB, DDR3 2400(O.C.)/2250(O.C.)/2200(O.C.)/2133(O.C.)/2000(O.C.)/1866/1600/1333/1 066 MHz Non-ECC, Un-buffered Memory Dual Channel Memory Architecture *Refer to www.asus.com or this user manual for the Memory QVL (Qualified Vendors Lists). Support AMD Memory Profile (AMP) memory *Due to OS limitation, when installing total memory of 4GB capacity or more, Windows® 32-bit operation system may only recognize less than 3GB. Install a 64-bit WindowsWindows® OS when you want to install 4GB or more memory on the motherboard. * The Max. 64GB memory capacity can be supported with DIMMs of 16GB (or above). ASUS will update QVL once the DIMMs are available on the market. Integrated AMD Radeon™ HD 7000 Series Graphics in Aseries APU Multi-VGA output support : HDMI/DVI/RGB ports - Supports HDMI with max. resolution 1920 x 1080 @ 60 Hz - Supports DVI with max. resolution 2560 x 1600 @ 60 Hz - Supports RGB with max. resolution 1920 x 1600 @ 60 Hz Maximum shared memory of 2048 MB AMD® Dual Graphics technology support * Supports DirectX 11 Supports AMD CrossFireX™ Technology 2 x PCIe 2.0 x16 (x16/x4) 2 x PCIe 2.0 x1 3 x PCI AMD A85X FCH(Hudson D4) chipset : 7 x SATA 6Gb/s ports (gray), gray 1 x SATA 6.0 Gb/s ports, red Support Raid 0, 1, 5, 10, JBOD Qualcomm Atheros, 1 x Gigabit LAN Controller Realtek® ALC887 8-Channel High Definition Audio CODEC - Supports : Jack-detection, Multi-streaming, Front Panel Jack-retasking Audio Feature : - Optical S/PDIF out port(s) at back panel a9970d27a52541fab47f463e86b002bb9b93ed86 0 524 2096 2017-11-01T19:13:41Z Pvdm 2 Created page with "<pre> [root]@amd64:~ # lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Expres..." wikitext text/x-wiki <pre> [root]@amd64:~ # lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03) 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 01:00.0 VGA compatible controller: NVIDIA Corporation G72 [GeForce 7500 LE] (rev a1) 02:00.0 Ethernet controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) [root]@amd64:~ # 8595e63583d840adf59495b0f31e1ec30912e4ea 0 497 2097 2075 2017-11-05T18:01:52Z Pvdm 2 /* how to extract images from pdf */ wikitext text/x-wiki scan pdf to file. first extract the pages and ocr them, then make one doc pdfimages -tiff input.pdf plaatje for i in *.tif; do tesseract $i tempje-$i; done cat tempje-plaatje-0*.txt >> docje.txt =Use tesseract to OCR a multi-page PDF file= First, convert the PDF to multiple TIFF files, because tesseract does not work with PDF. Number the files with 2 digits at the end, remove the alfa-channel: # convert -density 300 inputfile.pdf -depth 8 -alpha off outputfile_%02d.tiff Then, use tesseract to make it into text: # tesseract inputfile.tiff outputfile if you do not provide and extension for the outputfile, it will become .txt =Creating an overlay with the OCRed text= The newer version of Tesseract (3.03 RC at the time of writing this) can do this: *free, opensource and cross-platform *starting from version 3.03 PDF output is available *CLI software *multiple languages support *unfortunately, single image input, so to make a complete document, one must create a batch script to convert each page image to searchable PDF. After that PDF pages should be combined to a single PDF using tools like pdftk. This is the command: tesseract -l <lang> input.tif output pdf Note that in order to use this approach, the input PDF has to be rasterized first, since tesseract will not get PDF as input. =To combine multiple PDF files into one= # pdfunite output_*.pdf result.pdf =I have created a script= This script will do the work for you. Place the script in a directory together with the PDF to be processed, and run it. <pre> #!/bin/bash # converts a PDF containing scanned pages into a # new PDF file in which the OCRed text is overlayed, # making the PDF searchable on text strings. # use: # doit.sh nice.PDF # requires: tesseract-ocr, convert (ImageMagick), pdfunite, pdfinfo # 20170417 1.0 PvdM first version # 20170418 1.1 PvdM minor adjustment and improvements, mainly in the counter bestand="$1" newbestand=$(echo $bestand | cut -d"." -f1)_searchable.pdf teller="0" teller2="000" aantpaginas=$(pdfinfo "$bestand" | grep 'Pages:' | awk '{ print $2 }') RESTORE='\033[0m' RED='\033[00;31m' GREEN='\033[00;32m' YELLOW='\033[00;33m' BLUE='\033[00;34m' PURPLE='\033[00;35m' CYAN='\033[00;36m' LIGHTGRAY='\033[00;37m' function check_input { if [ -z "$bestand" ]; then echo - Error. Usage: echo " ./doit.sh input.pdf"; echo exit 1 fi } function check_error { if [ $? != 0 ]; then echo == Error! There was a problem in the command. exit 1 fi } clear echo "Converting PDF to searchable (overlay) PDF." echo -e "-------------------------------------------\n" check_input echo -e " $bestand contains $RED $aantpaginas $RESTORE pages.\n" echo " - (1/3) Extracting scanned PDF to images........" convert -density 300 "$bestand" -depth 8 -alpha off temp_%03d.tiff check_error echo -e " - Done.\n" echo echo " - (2/3) Doing OCR on the images..........." for i in temp_*.tiff; do tesseract -l eng $i temp_pdf_$teller2.pdf pdf check_error ((teller++)) teller2=$(printf "%05d" $teller) echo -e " - (2/3) Doing OCR on the images. $RED Page $teller/$aantpaginas done.$RESTORE" done echo -e " - Done.\n" echo echo " - (3/3) Combining the result into 1 (searchable) PDF" pdfunite temp_pdf_*.pdf "$newbestand" check_error echo -e " - Done. $RED'$newbestand'$RESTORE created.\n" rm temp* </pre> =examples= ==how to extract images from pdf== pdfimages -all sm_td20a_very_detailed.pdf . pdfimages -f 40 -l 41 -tiff hfe_teac_x-300_300r_service.pdf power-pcb c223b5bce6da86522b12331de76a520cb7bfba4e 0 525 2099 2017-11-08T14:16:25Z Pvdm 2 Created page with "*[[.vimrc]] *[[tips and tricks]]" wikitext text/x-wiki *[[.vimrc]] *[[tips and tricks]] c2418fdb3310edbc1adbdbd673f78b6c0e7f202b 0 526 2100 2017-11-08T14:19:05Z Pvdm 2 Created page with "To support the creation and editing of yaml files in vi, set the following in ~/.vimrc <pre> set expandtab set tabstop=2 set autoindent set shiftwidth=2 set softtabstop=2 set..." wikitext text/x-wiki To support the creation and editing of yaml files in vi, set the following in ~/.vimrc <pre> set expandtab set tabstop=2 set autoindent set shiftwidth=2 set softtabstop=2 set colorcolumn=3,5,7,9,11 set number </pre> e0f95c2528acad7ff7b6b18bf703a19234ba24da 0 527 2101 2017-11-08T16:09:57Z Pvdm 2 Created page with " Probably the best way to do this - assuming that you can't use the NOPASSWD solution provided by scottod is to use Mircea Vutcovici's solution in combination with Ansible va..." wikitext text/x-wiki Probably the best way to do this - assuming that you can't use the NOPASSWD solution provided by scottod is to use Mircea Vutcovici's solution in combination with Ansible vault. For example, you might have a playbook something like this: <pre> - hosts: all vars_files: - secret tasks: - name: Do something as sudo service: name=nginx state=restarted sudo: yes </pre> Here we are including a file called secret which will contain our sudo password. We will use ansible-vault to create an encrypted version of this file: ansible-vault create secret This will ask you for a password, then open your default editor to edit the file. You can put your ansible_sudo_pass in here. e.g.: secret: ansible_sudo_pass: mysudopassword Save and exit, now you have an encrypted secret file which Ansible is able to decrypt when you run your playbook. Note: you can edit the file with ansible-vault edit secret (and enter the password that you used when creating the file) The final piece of the puzzle is to provide Ansible with a --vault-password-file which it will use to decrypt your secret file. Create a file called vault.txt and in that put the password that you used when creating your secret file. The password should be a string stored as a single line in the file. From the Ansible Docs: .. ensure permissions on the file are such that no one else can access your key and do not add your key to source control Finally: you can now run your playbook with something like ansible-playbook playbook.yml -u someuser -i hosts --sudo --vault-password-file=vault.txt The above is assuming the following directory layout: <pre> . |_ playbook.yml |_ secret |_ hosts |_ vault.txt </pre> You can read more about Ansible Vault here: https://docs.ansible.com/playbooks_vault.html 3917ab0a6dfc4ae1194d1784696e2c1452e61a48 0 528 2110 2017-11-19T11:15:01Z Pvdm 2 Created page with "dit is de 'grote' usb wifi stick <pre> Product: 802.11n NIC usb 1-1.2: Manufacturer: Realtek usb 1-1.2: SerialNumber: E84E0642F576 RTL8192EU rev B (SMIC) 2T2R, TX queues 3, W..." wikitext text/x-wiki dit is de 'grote' usb wifi stick <pre> Product: 802.11n NIC usb 1-1.2: Manufacturer: Realtek usb 1-1.2: SerialNumber: E84E0642F576 RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0 usb 1-1.2: RTL8192EU MAC: e8:4e:06:42:f5:76 usb 1-1.2: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin usb 1-1.2: Firmware revision 19.0 (signature 0x92e1) usb 1-1.2: rtl8192eu_rx_iqk_path_b: Path B RX IQK failed! usbcore: registered new interface driver rtl8xxxu rtl8xxxu 1-1.2:1.0 wlp0s26u1u2: renamed from wlan0 IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u2: link is not ready e9ce8c505a620eebdb238ed8b5274b79646bf18e 0 534 2143 2142 2017-12-23T12:40:01Z Pvdm 2 wikitext text/x-wiki {| class="wikitable" |- ! Apparaat ! Wat is er mee ! Actie |- | Technics slp777 | ladesnaar slipt | vervangen |- | Sony DAT | row 2, cell 2 | row 2, cell 3 |} e1c118d86b0cf91b6ec2adbe6551718e5001ad2b 0 535 2146 2018-01-06T19:56:10Z Pvdm 2 Created page with "Edup: (steekt iets uit) <pre> Chipset:RTL8192CU Wireless Protocol:802.11a/g,802.11n Transmission rate:300mbps Interface Type:USB2.0 EDUP EP-N1557 300Mbps mini 2.4GHz wifi ada..." wikitext text/x-wiki Edup: (steekt iets uit) <pre> Chipset:RTL8192CU Wireless Protocol:802.11a/g,802.11n Transmission rate:300mbps Interface Type:USB2.0 EDUP EP-N1557 300Mbps mini 2.4GHz wifi adapter support windows and mac iOS 10.6~10.12 Note: Please install driver successfully before plug wireless adapter into your computer Please download the driver file here:http://www.szedup.com/support/driver-download/ep-n1557-driver/,if your desktop computer or laptop doesn't have CD rom. Specifications: Chipset RTL8192CU Standard IEEE802.11 a/b/g/n USB2.0 Built-in 1dBi antennas Frequency 2.4GHz Transmission speed 2.4G up to 300Mbps Support soft AP Operation system windows XP / Vista / 7 / 8 / 8.1 / 10 ,MAC OS X 10.12.X /10.11.X / 10.10.X / 10.9.X / 10.8.X /10.7.X/10.6.X/10.5.X/10.4.X Package content: 1*300Mbps wireless adapter ​1*Driver CD 20b29ae1475d679cea953d4c61842f86b754b809 0 532 2148 2147 2018-01-09T14:51:04Z Pvdm 2 wikitext text/x-wiki *Miles Davis - 1958 *Miles Davis - ESP *Miles Davis - 'Ascenseur pour l'Echafaud' *Miles Davis - The Legendary Stockholm Concert (March 22nd 1960) by Miles & Coltrane -- it's like Kind of Blue live. *Miles Davis - Essential Albums: Cookin'/Relaxin'/Workin'/Steamin' *Cannonball's Somethin' Else *Oliver Nelson's "Stolen Moments (1 song only) *Kenny Wheeler: The Widow in the Window (ECM) <- very good *Bobby Hutcherson: Patterns (Blue Note) <- beetje druk PVdM *Keith Jarrett: The Koln Concert (ECM) *Bill Evans Trio: Since We Met (Fantasy) *Wayne Shorter: Speak No Evil (Blue Note) *Pat Metheny: Bright Size Life (ECM) *Joe Henderson: Inner Urge (Blue Note) *Everybody Digs Bill Evans *Oscar Petersons Night Train ( PvdM ok) is amazing, along with his album of Cole Porter covers. *The Bridge - Sonny Rollins *Alice Coltrane's Journey in Satchidananda *Sarah Vaughan with Clifford Brown (singing) *A Love Supreme *Bill Evans Trio / The 1960 Birdland Sessions " Perhaps a long way from K.O.B. but it does have the spontaneous, timeless quality you are looking for. 63f0fad485ab79e24ad354357b464b91c8f51e0d 0 536 2159 2018-02-11T14:14:48Z Pvdm 2 Created page with "Belt: square. 1,5mm and lenght (flat=7cm) so 14cm, radius=~25mm Laser unit: SOAD70A" wikitext text/x-wiki Belt: square. 1,5mm and lenght (flat=7cm) so 14cm, radius=~25mm Laser unit: SOAD70A 286a454a573ad57f6cd21aeb61d22e734f6b0281 6 537 2169 2018-02-11T21:08:31Z Pvdm 2 dimensions of the pinch rollers on a Philips DCC600 wikitext text/x-wiki dimensions of the pinch rollers on a Philips DCC600 461b7ba8c81e0a4480834b3fb3cb3fb9c3e3ee99 0 538 2178 2177 2018-02-19T09:08:51Z Pvdm 2 wikitext text/x-wiki https://login.hotspotsvankpn.com/#login/e5cc556103e7b4326c8bdc55f3fed896 <pre> Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Users\pvdm>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Local Area Connection* 1: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Wi-Fi: Connection-specific DNS Suffix . : hotspots Link-local IPv6 Address . . . . . : fe80::9daa:b314:5819:3350%10 IPv4 Address. . . . . . . . . . . : 100.123.8.58 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : 100.123.0.1 Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : C:\Users\pvdm> </pre> linux <pre> ### Please remove (at least) this line when you modify the file! search hotspots nameserver 194.109.218.174 nameserver 194.109.218.175 </pre> <pre> 2: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 14:ab:c5:3d:7b:bf brd ff:ff:ff:ff:ff:ff inet 100.123.6.6/20 brd 100.123.15.255 scope global dynamic noprefixroute wlp1s0 valid_lft 1663sec preferred_lft 1663sec inet6 fe80::754b:f72:204b:d598/64 scope link noprefixroute valid_lft forever preferred_lft forever </pre> <pre> default via 100.123.0.1 dev wlp1s0 proto dhcp metric 600 100.123.0.0/20 dev wlp1s0 proto kernel scope link src 100.123.6.6 metric 600 </pre> 7c6647f2522084fa4cfcdb234b7c37ac13c9ba15 0 52 2184 2183 2018-03-24T14:15:36Z Pvdm 2 /* find */ wikitext text/x-wiki =Bash tips= <pre>^r Reverse search the command history ^a Return to the start of the command you're typing ^e Go to the end of the command you're typing ^u Cut everything before the cursor to a special clipboard ^k Cut everything after the cursor to a special clipboard ^y Paste from the special clipboard that Ctrl + u and Ctrl + k save their data to ^t Swap the two characters before the cursor (you can actually use this to transport a character from the left to the right, try it!) ^w Delete the word / argument left of the cursor ^l Clear the screen history lists command history !61 executes command on line 61 ls -l /etc/passwd stat !$ no need to repeat argument on second line man -k <keyword> searches in all man pages for <keyword> ls *.mp3 | xargs rm ls *.mp3 | xargs -i cp {} /home/bla ls *.mp3 -d -> stays in current dir and doesn't enter mp3/ </pre> * start a restricted shell (no cd, etc) to test programs # bash -r * start shell with options # bash -O [modification] autocd -> use the argument as cd command cd-spell -> corrects dir names dirspell -> corrects dir names in file completion no-caseglob -> case insensitive ---- to run commands: # command1 && command2 logical AND :: run command1, if ok then run command2 # command1 || command2 logical OR :: run command2 only if command1 fails =cp= cp -rv gives feedback cp -p preserves original date/time =dd= use blocks of 64k and report every 10Mb: dd if=/dev/hda | buffer -s 64k -S 10m > image or, from other console: kill -SIGUSR1 $(pidof dd) =df= df -type=ext3,ReiserFS df -H human readable =find= find all files in your homedir modified or created today find ~ -type f -mtime 0 case insentive search find . -iname "*mp3" find files and directories in yor homedir not created by you find ~ ! -user ${USER} and fix this find ~ ! -user ${USER} -exec sudo chown ${USER}:"{}" \; find duplicates PvdM find . -type f -exec md5sum '{}' ';' | sort | uniq --all-repeated=separate -w 15 =free= free -m -> megabytes free -t -> totals free -s[seconds] -> update interval watch the line with +/- buffers: '''free''' indicates memory that can be freed instantaniously '''used''' is all memory being used =grep= grep -A2 bla greps 2 lines after grep -B3 bla greps 3 lines before =history= # history -d [postition] -> remove specific command # history -c -> clear entire history =iotop= monitors io proces iotop -o makes output more readable by showing only processes causing io right now iotop -d10 refresh interval iotop -o -b -d10 -n30 > io.txt batch mode: write io status 30 times to file at 10s interval =iperf= iperf -s -w128k run server for performance benchmark iperf -c <serveraddress> -w128k -t30 -r run client iperf -c <serveraddress> -w128k -t30 -d run client in two directions, full duplex =kill= kill -l shows instructions 1 SIGHUP restart immediately after terminating, or triggers reconfiguration of background service 2 SIGINT Ctrl+c from the keyboard, terminate! 3 SIGQUIT Ctrl+\ from the keyboard, terminate with coredump 9 SIGKILL force terminate, extreme signal that can't ignored 11 SIGSEGV program attempted an invalid memory reference, terminate with coredump 15 SIGTERM request to terminate and cleanup 19 SIGSTOP interrupts the process until you enter SIGCONT to continue kill -19 9102 10234 stops several processes killall -19 ssh sends all ssh connections to sleep killall -19 -i ssh interactive mode (recommended) =lsof= lsof list open files lsof -i :22 list all ssh connections (same :ssh) lsof -i@10.0.0.1 list all connections from 10.0.0.1 lsof -i@amsterdam.nl list all connections from domain lsof -u username list all open files from username lsof -c bash list open files related to bash lsof -c /log/ list all open files from all processes containing log =lspci= lspci -v lspci -vv lspci -vvv lspci -nn -> show names & numerical lspci -k -> show kernel modules associated with the device =more or less= +<number> number of line from which to start displaying z <number> number of lines to jump forward y <number> number of lines to jump back -I ignore case when searching -V underline tabs, line endings /<ctrl-k> highlights all ocurrences of search =pgrep= pgrep ssh lists all ssh processes pgrep -l ssh shows names pgrep -f shows full commandline pgrep -u show user =ping= ping 0 -> pings localhost ping c 5 nu.nl -> pings 5 times ping -f host -> floods the host ping -a IP -> gives audible beep Note: It can give beep only from terminal number 1 through 7 and gnome-terminal ( It will not work in console ). ping -q ip -> show only summary ping -s 100 -> change packet size Pressing CTRL+| (Control key followed by pipe symbol) for the shows the summary in between, and continues with it packet sending and receiving process. ping hop1 hop2 hop3 .. hopN destination ping -R 192.168.1.63 -> Record and print route of how ECHO_REQUEST sent and ECHO_REPLY received =pkill= understands the same options as pgrep pkill -19 ssh pkill -19 -u joop stop joop's processes =ps= show how long a process is running ps -o pid,etime,cmd `pidof amarok` show memory usage per process ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS =pstree= pstree -a shows processes tree structure with program's parameters pstree -h highlights own process pstree -H <id> highlights process id pstree -u shows user =stat= shows status of file stat /etc/passwd stat -c "%x %n" /etc/passwd formatted to show time =swapon= swapon -s see size and usage =tail or head= --retry keep monitoring the file -s seconds how often monitoring retry -pid <pid> stops tail from running if PID stops running =tar= tar zxf <file> -> extracts file =top= <pre> PID programma id USER gebruiker PR prioriteit van de taak NI nice value VIRT virtuele geheugen gebruik RES fysieke geheugen gebruik SHR deel v/h gebeugen dat mogelijk met andere taken wordt gedeeld %CPU percentage processorgebruik %MEM percentage geheugengebruik TIME+ de tijd dat de taak op de cpu heeft gedraaid COMMAND de naam van de taak </pre> keys: z: enable color mode. x: show sorted column in different color < >: change sorted column u [user]: show only users processes d: delay in sec show only user user #top -u user =zombies= ps aux | grep defunct =AutoYast= create autoyast file through icon in Yast2->autoyast www.suse.de/~ug (Uwe Gansert) =Midnight Commander (MC)= The standard colorpallette is incredibly hard to read in certain terminals, like yakuake. For readable colors (mostly black and green), enter in your ~/.mc/ini file the following line: [Colors] base_color=lightgray,green:normal=green,default:selected=white,gray:marked=yellow,default:markselect=yellow,gray:directory=blue,default:executable=brightgreen,default:link=cyan,default:device=brightmagenta,default:special=lightgray,default:errors=red,default:reverse=green,default:gauge=green,default:input=white,gray:dnormal=green,gray:dfocus=brightgreen,gray:dhotnormal=cyan,gray:dhotfocus=brightcyan,gray:menu=green,default:menuhot=cyan,default:menusel=green,gray:menuhotsel=cyan,default:helpnormal=cyan,default:editnormal=green,default:editbold=blue,default:editmarked=gray,blue:stalelink=red,default =tune kernelparameters= stored in /proc/sys/ gone after reboot sysctl is a service that reads sysctl.conf during boot and read parameters from there -> makes it permanent # ulimit -a givesinfo about system resources limitations 061e091749fbaff17f5b65ecd777aa1b5e6f94fc 0 539 2198 2197 2018-05-19T18:27:28Z Pvdm 2 /* identificatie */ wikitext text/x-wiki =identificatie= Kogellagers zijn in verregaande mate gestandaardiseerd. Nummercodes identificeren een specifiek type kogellager. Meestal is op het kogellager de nummercode gestanst. C-aanduidingen zeggen iets over de speling van de binnenring t.o.v. de buitenring binnen het lager. C3 is de meest voorkomende variant. Dit is een lager dat gelijk is aan zijn C0 genummerde broertje met uitzondering van de speling, die is dus groter. Men heeft ook nog C1 die heeft een veel kleinere speling dan C0 (de standaardmaat) en C2 met een kleiner speling dan C0, maar iets groter dan C1. Verder is er naast de genoemde C3 ook nog een C4 en C5, die hebben een nog grotere speling. '''In volgorde van speling beginnende bij de strakste zijn de codes: C1, C2, C0, C3, C4 en C5.''' Bij inline-skates is de Amerikaanse onderverdeling ABEC standaard. De schaal loopt van ABEC 1 tot ABEC 9 (de nauwkeurigste lagers). =coderingen= <div style="text-align:center;">Overzicht codering toevoegingen inzake afdichting & speling</div> {| style="border-spacing:0;width:6.6931in;" |- style="border:none;padding:0in;" | align=center| || '''SKF''' || '''FAG''' || '''NTN''' || '''SNR''' || '''NKE''' || '''Koyo''' || '''NSK''' || '''Nachi''' |- | style="border:none;padding:0in;" | '''1-zijdige metaal-afdichting''' || Z || Z || Z || Z || Z || Z || Z || Z |- | style="border:none;padding:0in;" | '''1-zijdige rubber-afdichting''' || RS1/RSH || RSR || LU || E || RSR/RS2 || RS || DU || Z |- | style="border:none;padding:0in;" | '''2-zijdige metaal-afdichting''' || 2Z || 2Z || ZZ || ZZ || 2Z || ZZ || ZZ || ZZ/ZZE |- | style="border:none;padding:0in;" | '''2-zijdige rubber-afdichting''' || 2RS1/2RSH || 2RSR/C-2HRS || LLU || EE || 2RSR/2RS2 || 2RS || DDU || 2SNL/2NSE |- | style="border:none;padding:0in;" | '''speling groter dan normaal''' || C3 || C3 || C3 || J30 || C3 || C3 || C3 || C3 |- | style="border:none;padding:0in;" | '''speling groter dan C3''' || C4 || C4 || C4 || C4 || C4 || C4 || C4 || C4 |- | style="border:none;padding:0in;" | '''speling kleiner dan normaal''' || C2 || C2 || C2 || C2 || C2 || C2 || C2 || C2 |- |} <div style="color:#333333;margin-left:0in;margin-right:0in;">Tot slot nog een paar opmerkingen.</div> * <div style="color:#333333;margin-left:0in;margin-right:0in;">Lagers waarbij geen toevoeging is vermeld, hebben geen afdichting daar bij de toepassing rekening gehouden word met de (constante) smering van het lager;</div> * <div style="color:#333333;">Lagers die een 2Z afdichting hebben zijn stofdicht en hebben een hoger maximaal toerental dan de rubber afgedichte varianten;</div> * <div style="color:#333333;">Lagers die een 2RS1 afdichting hebben zijn spatwaterdicht. Dit betekent overigens geenszins dat deze lagers waterdicht zijn!;</div> * <div style="color:#333333;">RVS lagers worden aangeduid met een S en W voor de codering van het lager. Bijvoorbeeld SKF W6004 2RSH of ECO S6004 2RS</div> =tabel= <div style="color:#333333;margin-left:0in;margin-right:0in;">In onderstaande tabel staan de meest gangbare coderingen voor kogellagers, m.u.v. spanring kogellagers,spindellagers en vierpunts-kogellagers. Doordat de lagerfabrikanten niet allemaal dezelfde lageraanduidingen gebruiken, kan het zijn dat er voor een bepaalde eigenschap verschillende afkortingen bestaan.</div> {| style="border-spacing:0;width:14.9604in;" |- | style="border:none;padding:0in;" | '''SKF''' | style="border:none;padding:0in;" | '''FAG''' | style="border:none;padding:0in;" | '''NTN''' || || |- || 2RS12RSH || 2RSRC-2HRS || LLU || : || spatwaterdichte slepende afdichting van rubber met wapening van staalplaat aan beide zijdes van het lager |- || 2RSL || || || : || wrijvingsarme variant van 2RS1 |- || 2RZ || || || : || wrijvingsarme variant van 2RS1 |- || 2Z || 2Z || ZZ || : || geperst stalen beschermplaatje (stofafdichting) aan beide zijdes van het lager |- || A || || || : || hoek is 30 graden (1-rijig hoekcontactkogellager) |- || A || || || : || geen vulopeningen + hoek is 30 graden &nbsp; (SKF 2-rijige hoekcontactkogellager) |- || B || B || B || : || hoek is 40 graden (1-rijig hoekcontact kogellager) |- || || B || || : || hoek is 25 graden (FAG 2-rijige hoekcontactkogellager) |- || C2 || C2 || C2 || : || radiale speling kleiner dan normaal |- || C2 || || || : || axiale speling kleiner dan CB (2-rijige hoekcontactkogellager) |- || C3 || C3 || C3 || : || radiale speling groter dan normaal |- || C3 || || || : || axiale speling groter dan CB (2-rijige hoekcontactkogellager) |- || C4 || || || : || radiale speling groter dan C3 |- || C5 || || || : || radiale speling groter dan C4 |- || CA || || || : || lager voor gepaarde montage, bij O- of X-opstelling is de axiale speling in ongemonteerde toestand kleiner dan CB |- || CB || UA || || : || lager voor gepaarde montage, bij O- of X-opstelling is de axiale speling in ongemonteerde toestand normaal |- || CB || || || : || speciale axiale speling&nbsp; (2-rijige hoekcontactkogellager) |- || CC || || || : || lager voor gepaarde montage, bij O- of X-opstelling is de axiale speling in ongemonteerde toestand groter dan CB |- || D || DA || || : || gedeelde binnenring (2-rijige hoekcontactkogellager) |- || DB || DB || || : || 2 gepaarde kogellagers in O-opstelling |- || DF || DF || || : || 2 gepaarde kogellagers in X-opstelling |- || DT || DT || || : || 2 gepaarde kogellagers in tandem-opstelling |- || E || || || : || geoptimaliseerde inwendige constructie hoekcontactkogellagers |- || F || || || : || massief stalen vensterkooi hoekcontact kogellager |- || GA || UL || || : || lager gepaarde montage; bij O- en X-opstelling is er in ongemonteerde toestand een lichte voorspanning |- || GB || || || : || lager gepaarde montage; bij O- en X-opstelling is er in ongemonteerde toestand een matige voorspanning |- || GC || || || : || lager gepaarde montage; bij O- en X-opstelling is er in ongemonteerde toestand een zware voorspanning |- || || UO || BG || : || lager gepaarde montage; bij O- en X-opstelling is in ongemonteerde toestand spelingsvrij |- || J || JP || J || : || geperste kooi van staal, op de kogels gecenteerd |- || J1 || || || : || idem J&nbsp; (2-rijige hoekcontactkogellager) |- || K || K&nbsp; || || : || Conische boring |- || M || M / MP || L1 || : || messing kooi op kogels gecenteerd |- || MA || MA || || : || messing kooi op buitenring gecenteerd |- || MB || || || : || messing kooi op binnenring gecenteerd |- || N || || || : || borgringgroef in de buitenring |- || N1 || || || : || 1 borggroef op zijvlak buitenring |- || NR || || || : || borgringgroef in de buitenring + borgring |- || P || || || : || kooi van glasvezelversterkte polyamide bij hoekcontact kogellagers |- || P5 || || || : || maat- en loopnauwkeurigheid ISO 5 |- || P52 || || || : || P5 + C2 |- || P6 || || || : || maat- en loopnauwkeurigheid ISO 6 |- || P62 || || || : || P6 + C2 |- || P63 || || || : || P6 + C3 |- || PH || || || : || kooi van glasvezelversterkte polyether-etherketone (PEEK) bij hoekcontact kogellagers |- || RS1/RSH || RSR || LU || : || spatwaterdichte slepende afdichting van rubber met wapening van staalplaat aan een zijde van het lager |- || RSL || || || : || wrijvingsarme variant van RS1 |- || RZ || || || : || wrijvingsarme variant van RS1 |- || TH || || || : || kooi van vezelversterkte fenolhars op kogels gecentreerd |- || TN || || || : || kooi van polyamide op kogels gecentreerd |- || TN9 || TVP/TVH || || : || kooi van glasvezelversterkte polyamide op kogels gecentreerd |- || TNH || || || : || kooi van glasvezelversterkte polyether-etherketone (PEEK) op kogels gecentreerd |- || Y || Y || || : || geperste kooi van messing, op de kogels gecenteerd |- || Z || Z || || : || geperst stalen beschermplaatje (stofafdichting) aan een zijde van het lager |- |} <div style="color:#333333;margin-left:0in;margin-right:0in;">Voorbeelden:</div> # <div style="color:#333333;margin-left:0.3646in;margin-right:0in;">SKF 6005 2RSH = groefkogellagers met spatwaterdichte slepende afdichting van rubber met wapening van staalplaat aan beide zijdes van het lager;</div> # <div style="color:#333333;margin-left:0.3646in;margin-right:0in;">FAG 3202B 2RSR TVH = 2-rijige hoekcontactkogellager met een hoek van 25 graden, kooi van glasvezelversterkte polyamide op kogels gecentreerd en spatwaterdichte afdichting;</div> =uitleg= <div style="color:#333333;margin-left:0in;margin-right:0in;">Deze codering is officieel als volgt:</div> <div style="color:#333333;margin-left:0in;margin-right:0in;"><span style="color:#ff0000;">'''voorvoegsel</span><span style="color:#000000;">&nbsp;-&nbsp;</span><span style="color:#008000;">hoofdnummer</span><span style="color:#000000;">&nbsp;-&nbsp;</span>volgcode_A&nbsp;<span style="color:#ff0000;">volgcode_B</span>&nbsp;<span style="color:#ffcc00;">volgcode_C&nbsp;</span><span style="color:#cc0099;">/</span><span style="color:#ffcc00;">&nbsp;</span><span style="color:#666633;">volgcode_D1 t/m D6'''</span></div> <div style="color:#333333;margin-left:0in;margin-right:0in;">Je ziet dat deze codering vrij ingewikkeld is. Immers: niet altijd wordt het voorvoegsel of worden de volgcodes allemaal gegeven.Het is dus ook goed mogelijk dat alleen het hoofdnummer en volgcode B wordt gegeven.</div> <div style="color:#333333;margin-left:0in;margin-right:0in;">Stel je voor dat je een lager&nbsp;'''DIN625 6201Z'''&nbsp;hebt. Wat voor lager heb je dan? Dat is de vraag die we hier gaan beantwoorden.Aan het eind van deze faq kan jij dit decoderen. Dus lees snel verder.</div> = Voorvoegsel = <div style="color:#333333;margin-left:0in;margin-right:0in;">Het voorvoegsel wordt zelden genoemd. Daarom zal ik die hier niet bespreken.</div> = Hoofdnummer = <div style="margin-left:0in;margin-right:0in;"><span style="color:#333333;">Veel voorkomende lagers zijn hieronder te vinden, met hun maten.</span><span style="color:#333333;">Alle lagers zijn in Z, ZZ, RS en RS2 verkrijgbaar.</span><span style="color:#333333;">De maten zijn in&nbsp;</span><span style="color:#333333;">'''millimeters'''</span><span style="color:#333333;">&nbsp;</span><span style="color:#333333;">weergeven.</span></div> {| style="border-spacing:0;width:3.5007in;" |- style="background-color:transparent;border:none;padding:0in;" | align=center| '''Code''' | align=center| '''d'''Diameter binnen | align=center| '''D'''Diameter buiten | align=center| '''B'''Hoogte |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6000 | align=center| 10 | align=center| 26 | align=center| 8 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6200 | align=center| 10 | align=center| 30 | align=center| 9 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6300 | align=center| 10 | align=center| 35 | align=center| 11 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6001 | align=center| 12 | align=center| 28 | align=center| 8 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6201 | align=center| 12 | align=center| 32 | align=center| 10 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6301 | align=center| 12 | align=center| 37 | align=center| 12 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6002 | align=center| 15 | align=center| 32 | align=center| 9 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6202 | align=center| 15 | align=center| 35 | align=center| 11 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6302 | align=center| 15 | align=center| 42 | align=center| 13 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6003 | align=center| 17 | align=center| 35 | align=center| 10 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6203 | align=center| 17 | align=center| 40 | align=center| 12 |- style="background-color:transparent;border:none;padding:0in;" | align=center| 6303 | align=center| 17 | align=center| 47 | align=center| 14 |- |} <div style="color:#333333;margin-left:0in;margin-right:0in;">De hoofdcode uit het voorbeeld is&nbsp;'''6201'''. We gaan dit als eerste decoderen.De hoofdcode bestaat uit cijfers en is gerelateerd aan het soort lagers en de grootte ervan.Het eerste cijfer geeft het soort lagers weer. In het voorbeeld is dat dus een&nbsp;'''6'''.</div> {| style="border-spacing:0;width:3.0021in;" |- style="border:none;padding:0in;" || '''code''' || '''verklaring''' |- style="border:none;padding:0in;" || 0 || Dubbelrijig hoekcontact lagers |- style="border:none;padding:0in;" || 1 || Zelfinstellend kogellagers |- style="border:none;padding:0in;" || 2 || Tonlagers |- style="border:none;padding:0in;" || 3 || Kegellagers |- style="border:none;padding:0in;" || 4 || Tweerijig groef kogellagers |- style="border:none;padding:0in;" || 5 || Axiale kogellagers |- style="border:none;padding:0in;" || 6 || Groef kogellagers |- style="border:none;padding:0in;" || 7 || Hoekcontact lagers |- style="border:none;padding:0in;" || 8 || Axiale cilinder lagers |- style="border:none;padding:0in;" || N || cilinderlagers |- |} <div style="color:#333333;margin-left:0in;margin-right:0in;">Het lager in het voorbeeld is dus een&nbsp;'''Groef kogellager'''. Dit het meest 'gewone' kogellager wat wij kennen. Dus een gewoon lager.</div> <div style="color:#333333;margin-left:0in;margin-right:0in;">De rest van de cijfers van de hoofdcode geven de maatvoering aan.</div> == Volgcode's A t/m D == <div style="color:#333333;margin-left:0in;margin-right:0in;">De volgcode's A t/m C worden door een spatie gescheiden.Meestal is er maar een van de 3 code's aanwezig.&nbsp;Indien er een volgcode C is aangegeven, is er nooit een volgcode D opgegeven.</div> = Volgcode A = <div style="color:#333333;margin-left:0in;margin-right:0in;">De volgcode A geeft informatie over het&nbsp;'''inwendige'''&nbsp;van het lager.Dit zal niet vaak voorkomen.</div> {| style="border-spacing:0;width:10.0382in;" |- style="border:none;padding:0in;" || '''code''' || '''verklaring''' |- style="border:none;padding:0in;" || A || Speciaal ontwerp voor speciale toepassing |- style="border:none;padding:0in;" || A || Contacthoek 30 Graden bij hoekcontact lagers |- style="border:none;padding:0in;" || B || Contacthoek 40 graden bij hoekcontact lagers |- style="border:none;padding:0in;" || B || Contacthoek kleiner dan 17 graden bij kegel lagers |- style="border:none;padding:0in;" || C || Contacthoek 15 graden bij hoekcontact lagers |- style="border:none;padding:0in;" || C || Contacthoek 20 graden bij kegel lagers |- style="border:none;padding:0in;" || CA || Contacthoek 20 graden bij hoekcontact lagers |- style="border:none;padding:0in;" || D || Contacthoek 28 graden en 30 minuten voor kegel lagers |- style="border:none;padding:0in;" || DJ || Contacthoek 28 graden en 48 minuten en 39 seconden voor kegel lagers |- style="border:none;padding:0in;" || E || Contacthoek 35 graden bij hoekcontact lagers |- style="border:none;padding:0in;" || J || Bepaalde maten van een kegellager voldoen aan de ISO standaard |- |} = Volgcode B = <div style="color:#333333;margin-left:0in;margin-right:0in;">Deze volgcode B geeft aan hoe de&nbsp;'''afdichting'''&nbsp;is bij het lager.</div> {| style="border-spacing:0;width:5.7889in;" |- style="border:none;padding:0in;" || '''code''' || '''verklaring''' |- style="border:none;padding:0in;" || (geen code) || het lager is aan beide kanten open |- style="border:none;padding:0in;" || RS &nbsp;/ RS1 &nbsp;/ RSH || het lager is aan een zijde spatwater dicht dmv 1 rubberen afdichtring |- style="border:none;padding:0in;" || 2RS / 2RS1 / 2RSH || het lager is aan twee zijden spatwaterdicht dmv 2 rubberen afdichtringen |- style="border:none;padding:0in;" || RSL || het lager is aan een zijde spatwaterdicht met extra lage wrijving |- style="border:none;padding:0in;" || 2RSL || het lager is aan twee zijden spatwaterdicht met extra lage wrijving |- style="border:none;padding:0in;" || Z || het lager is aan een zijde stofdicht dmv 1 metalen plaatje |- style="border:none;padding:0in;" || 2Z = ZZ || het lager is aan twee zijden stofdicht dmv 2 metalen plaatjes |- |} <div style="color:#333333;margin-left:0in;margin-right:0in;">Het lager in het voorbeeld heeft bij volgcode B een&nbsp;'''Z'''. Dit geeft dus aan dat dit lager aan 1 kant is dichtgemaakt met een metalen plaatje.</div> = Volgcode C = <div style="color:#333333;margin-left:0in;margin-right:0in;">Deze volgcode C geeft informatie over de&nbsp;'''kooiconstructie'''. Dus over de 2 stalen ringen waarin de kogel draaien.</div> {| style="border-spacing:0;width:3.6556in;" |- style="border:none;padding:0in;" || '''code''' || '''verklaring''' |- style="border:none;padding:0in;" || (geen code) || standaard: massief ijzeren kooi |- style="border:none;padding:0in;" || F || Massieve ijzeren kooi |- style="border:none;padding:0in;" || J || Geperste plaatstalen kooi |- style="border:none;padding:0in;" || L || Massieve lichtmetalen kooi |- style="border:none;padding:0in;" || M || Massieve messing kooi |- style="border:none;padding:0in;" || P || Met glasvezel versterkte polyamide kooi |- style="border:none;padding:0in;" || Y || Geperste kooi ven messing plaat |- |} = Volgcode D = <div style="color:#333333;margin-left:0in;margin-right:0in;">Achter het&nbsp;<span style="color:#cc0099;">'''/'''</span>&nbsp;teken staan de kenmerken t.a.v. materiaal,hittebehandeling, nauwkeurigheid,extra speling, smering e.d..</div> {| style="border-spacing:0;width:9.1569in;" |- style="border:none;padding:0in;" || '''code''' || '''categorie''' || '''verklaring''' |- style="border:none;padding:0in;" || P0 || Nauwkeurigheid || klasse 0 van de ISO tolerantie-klassen = ABEC 1 |- style="border:none;padding:0in;" || P2 || Nauwkeurigheid || klasse 0 van de ISO tolerantie-klassen = ABEC 9 |- style="border:none;padding:0in;" || P4 || Nauwkeurigheid || klasse 0 van de ISO tolerantie-klassen = ABEC 7 |- style="border:none;padding:0in;" || P5 || Nauwkeurigheid || klasse 0 van de ISO tolerantie-klassen = ABEC 5 |- style="border:none;padding:0in;" || P6 || Nauwkeurigheid || klasse 0 van de ISO tolerantie-klassen = ABEC 3 |- style="border:none;padding:0in;" || C1 || Extra speling || Krappere speling dan bij C2 |- style="border:none;padding:0in;" || C2 || Extra speling || Krappere speling dan bij C3 |- style="border:none;padding:0in;" || C3 || Extra speling || Speling normaal |- style="border:none;padding:0in;" || C4 || Extra speling || Ruimere speling dan bij C3 |- style="border:none;padding:0in;" || C5 || Extra speling || Ruimere speling dan bij C4 |- |} = Het voorbeeld uitgelegd = <div style="color:#333333;margin-left:0in;margin-right:0in;">Het voorbeeld wat is gaf was een DIN625 6201Z. We gaan nu kijken wat dat betekent:</div> {| style="border-spacing:0;width:11.3354in;" |- style="border:none;padding:0in;" || DIN625 || Duitse Industrie Norm 625 || Dit betekent dat het een kogellager is |- style="border:none;padding:0in;" || 6201 || Hoofdnummer || Dit geeft de afmetingen aan: 12mm binnendiameter; 32mm buitendiameter en 10mm dikte |- style="border:none;padding:0in;" || Z || Volgcode B || Dit geeft aan dat het lager aan 1 kant stofdicht is met een metalen plaatje |- |} 17892561e9c3c362904d4ef6ef062716109812df 0 507 2204 2037 2018-07-26T15:13:14Z Pvdm 2 wikitext text/x-wiki *[[system info tecra]] *[[how to get into bios-setup]] *[[partitions tecra]] *[[performance harddisk]] BIOS: when keyboardlight comes on, press and hold F2 8e9fcad3837f2558f413617dad6fcb4e69901c77 0 540 2207 2206 2018-07-26T15:25:52Z Pvdm 2 wikitext text/x-wiki =orginele harddisk= <pre> /dev/sda: Model=TOSHIBA THNSNK128GVN8, FwRev=K8TA4101, SerialNo=17CS14H7T8GT Config={ Fixed } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=250069680 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: Unspecified: ATA/ATAPI-3,4,5,6,7 * signifies the current active mode tecra:~ # hdparm -T /dev/sda /dev/sda: Timing cached reads: 13074 MB in 1.99 seconds = 6579.23 MB/sec tecra:~ # hdparm -T /dev/sda /dev/sda: Timing cached reads: 13082 MB in 1.99 seconds = 6583.21 MB/sec ^[[Atecra:~ # hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 1428 MB in 3.00 seconds = 475.35 MB/sec tecra:~ # hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 1404 MB in 3.00 seconds = 467.92 MB/sec tecra:~ # </pre> =evo 970= 410475435f8ead6c968e4807feb1fd0a7403ae34 0 516 2216 2215 2018-08-08T14:36:37Z Pvdm 2 /* Dit is de 1e webcam */ wikitext text/x-wiki =Dit is de 1e webcam= Oftewel ICAM-608 IHOMECAM MAC: 00:ED:AC:4F:BF:B9 http://192.168.1.30:8888/index.htm http://192.168.1.30:8888/jpeg.html http://192.168.1.30:8888/videostream.cgi http://192.168.1.30:8888/videostream.cgi?user=admin&pwd= Zoneminder: HTTP, simple, IP, port, Remote Host Path:/videostream.cgi?user=admin&pwd= , 640x360 HTTP, Regexp, 192.168.1.30, 8888, /videostream.cgi?user=admin&pwd=admin, 24 bit color, 640x360 =camera1.conf= <pre> cat camera1.conf #PVDM camera_id = icam608 lext_left CAMERA1 width 1280 height 720 netcam_url http://192.168.1.30:8888/videostream.cgi?user=admin&pwd= netcam_keepalive on target_dir /data/motion/ picture_filename CAM1-%q 199b03e7fe21b0ff1da75158180ed0c9a75d2d7a 0 126 2220 673 2018-08-15T10:53:14Z Pvdm 2 Pvdm moved page [[Quadroponic or DTS surround sound]] to [[Quadrophonic or DTS surround sound]] wikitext text/x-wiki qoute: <pre> Some of my favorite quadraphonic titles: Sound effects with Boeing 707 and 727 takeoff and landings. Pink Floyd – Dark Side Of The Moon The Moody Blues – Days Of Future Passed The Moody Blues – Every Good Boy Deserves A Favor The Moody Blues – Seventh Sojourn Edger Winter Group – They Only Come Out At Night The Doobie Brothers – The Captain & Me The Doobie Brothers – Toulouse Street Earth Wind & Fire – That’s The Way Of The World Earth Wind & Fire – Open Our Eyes Ohio Players – Honey Quincy Jones – You’ve Got It Bad Girl Burt Bacharach – Reach Out The Carpenters – A Song For You The Carpenters – Close To You Steely Dan – Countdown To Ecstasy Deep Purple – Machine Head Black Sabbath – Paranoid Chick Corea & Return To Forever – Musicmagic Sergio Mendes – (self title) Jeff Beck – Blow By Blow Maynard Ferguson - Conquistador Enoch Light – Sounds of Burt Bacharach I still have these but it's been years since I played them. Still have a SQ decoder laying around too. ALLMAN BROTHERS EAT A PEACH BAEZ, JOAN BLESSED ARE BAEZ, JOAN FROM THE SHADOWS BAEZ, JOAN GREATEST HITS AND MORE BENSON, GEORGE BODY TALK BERNSTEIN-NYP ALSO SPRAC ZARASTRUSA BERNSTEIN-NYP HIGHLIGHTS FROM MASS BERNSTEIN-NYP MASS BLACK SABBATH PARANOID BLOOD, SWEAT AND TEARS BLOOD, SWEAT & TEARS BLOOD, SWEAT AND TEARS GREATEST HITS BLOOD, SWEAT AND TEARS NEW BLOOD CARLOS, WALTER SWITCHED ON BACH CARPENTERS THE SINGLES CHASE CHASE CORYELL, LARRY OFFERINGS CORYELL, LARRY INTRODUCTING THE ELEVENTH HOUSE COUNTRY JOE & THE FISH THE LIFE AND TIMES OF DAVIS, MILES BITCHES BREW DAVIS, MILES LIVE EVIL DEEP PURPLE MACHINE HEAD DEEP PURPLE STORMBRINGER DEODATO DERRINGER, RICK ALL AMERICAN BOY DERRINGER, RICK RICK DERRINGER DOORS THE BEST OF THE DOORS DYLAN, BOB NASHVILLE SKYLINE DYLAN, BOB DESIRE DYLAN, BOB PLANET WAVES GRASSROOTS SIXTEEN GREATEST HITS EARTH, WIND AND FIRE THE WAY OF THE WORLD HANCOCK, HERBIE HEADHUNTERS JEFFERSON AIRPLANE VOLUNTEERS JETHRO TULL AQUALUNG JETHRO TULL WAR CHILD JOPLIN, JANIS PEARL KING, BB FRIENDS KING, CAROLE MUSIC KOOPER,BLOOMFIELD,STILLS SUPERSESSION KRISOFFERSON, KRIS THE SILVER TONGUE DEVIL KRISOFFERSON, KRIS BORDER LORD KRISOFFERSON, KRIS JESUS WAS A CAPRICORN LOGGINS AND MESSINA LOGGINS AND MESSINA LOGGINS AND MESSINA FULL SAIL MAHAVISNU ORCHESTRA BIRDS OF FIRE MAHAVISNU ORCHESTRA FROM NOTHINGNESS TO ETERN MASON, DAVE DAVE MASON MASON, DAVE IT'S LIKE YOU NEVER LEFT MASON, DAVE SPLIT COCONUTS MILES, BUDDY CHAPTER VIII MOTT THE HOOPLE THE HOOPLE MOUNTAIN THE BEST OF MOUNTAIN AVALANCHE WEST,BRUCE AND LAING WHY DONCHA WEST,BRUCE AND LAING WHAT EVER TURNS YOU ON NEKTAR REMEMBER THE FUTURE NEKTAR DOWN TO EARTH NEW RIDER OF THE PURPLE SAGE PANAMA RED OLDFIELD, MIKE BOXED (TUBULAR BELLS, HEREST RIDGE, OMMADAWN) OLDFIELD, MIKE EXPOSED PINK FLOYD ATOM HEART MOTHER PINK FLOYD DARK SIDE OF THE MOON PINK FLOYD WISH YOU WERE HERE POCO DELIVERIN' POCO SEVEN POCO CANTANMOS REDBONE MESSAGE TO THE NATION REO SPEEDWAGON PAUL REVERE & THE RAIDERS INDIAN RESERVATION SANTANA ABRAXIS SANTANA III SANTANA AND BUDDY MILES CARLOS SANTANA AND BUDDY MILES SANTANA CARAVANSERI SANTANA LOTUS SANTANA WELCOME SANTANA BORBOLETTO SANTANA & McLAUGHLIN LOVE DEVOTION & SURRENDER SANTANA & ALICE COLTRANE INNERVISIONS SANTANA BEST OF GARFUNKEL, ART ANGEL CLAIRE GARFUNKEL, ART BREAKAWAY SLY AND THE FAMILY STONE GREATEST HITS SLY AND THE FAMILY STONE SMALL TALK STEVENS, CAT FOREIGNER STREISAND, BARBARA STONEY END STREISAND, BARBARA LIVE AT THE FORMUN STREISAND, BARBARA BARBARA JOAN STRIESAND STREISAND, BARBARA LAZY AFTERNOON SUBOTNIC, MORTON TOUCH TEN YEARS AFTER A SPACE IN TIME THREE DOG NIGHT HARD LABOR THREE DOG NIGHT VAN LEER, THIJS INTROSPECTION VAN LEER, THIJS INTROSPECTION 2 WAKEMAN, RICK THE SIX WIVES OF HENRY THE VIII WAKEMAN, RICK THE SIX WIVES OF HENRY THE VIII WALSH, JOE SMOKER YOU DRINK THE PLAYER YOU GET WEATHER REPORT MYSTERIOUS TRAVELER WEATHER REPORT TALE SPINNING WINTER, EDGAR THEY ONLY COME OUT AT NIGHT WINTER, EDGAR SHOCK TREATMENT WINTER, JOHNNY STILL ALIVE AND WELL WINTER, JOHNNY SAINT AND SINNER WINTER, JOHNNY JOHN DAWSON WINTER III ZAPPA, FRANK OVERNIGHT SENSATION ZAPPA, FRANK APOSTRIE </pre> 7a5cd47b5a3c5a49d40b803dc15679ec8005a1a4 0 542 2221 2018-08-15T10:53:14Z Pvdm 2 Pvdm moved page [[Quadroponic or DTS surround sound]] to [[Quadrophonic or DTS surround sound]] wikitext text/x-wiki #REDIRECT [[Quadrophonic or DTS surround sound]] 45a08801acd8b57602248d6f6ee7b5c86af0fbc3 0 437 2224 1639 2018-08-15T11:17:49Z Pvdm 2 wikitext text/x-wiki 1979 (cont.)... TEAC introduced the '''A3440''' 1/4 inch multitrack, an upgraded 4- track open reel recorder. Even thought the A3440S had the TEAC brand name, it was sold by the TASCAM sales organization through music stores. 1983...TASCAM introduced the 30 series recorders. The TASCAM 38 was a 1/2", 8-track, 10 1/2" reel-to-reel recorder. Introductory price was under $3,000. The 38 filled a niche for the serious entry level recordist. The TASCAM 34 was a 4 track recorder with full frequency response in Sync Mode at an inexpensive price. The TASCAM 32 was a half track master recorder/reproducer using 1/4" tape. 1986- '''Tascam 34B''' 1991- The TASCAM 1500 Series were 4-buss recording consoles with 8 directly assignable outputs. The M1500 series included an 8-input version, the M1508, and a 16-input version, the '''M1516.''' ===== Full history: Teac/Tascam models list rom our ads and catalog collection {| style="border-spacing:0;" || '''1960''' - Teac 505 |- || '''1961''' - Concertone 505 |- || '''1966''' - A-610, A-5050, A-4010S, A-3010, A-1200, A-4020, A-2020, A-1600, A-1500,R-310 |- || '''1967''' - R-1000, R-1100, A-4010, A-4020, A-2020 |- || '''1968''' - A-4010S, AS-200, A-6010, A-1200 |- || '''1969''' - R-310, A-1200U, A-6010, A-4010S, A-4010 SRA Quad |- || '''1970''' - A-100, A-1200, A-1500, A-1500U, A-6010, A6010U, A-7030, TCA-40, TCA-41, TCA-42 |- || '''1971''' - A-1200U, A-1500, A-6010U, A-7010U, A-7030U, A-3300, 4010SL, 6010SL, 7010SL, 7030SL, 3300-10, 3300-11, 3300-12, 1230, 1250, 4070, A-1200, TCA-40, TCA-41, TCA-42, An-180, AN-80, An-50 |- || '''1972''' - 2340, 3340, TCA-43 (1st Simul-Sync), A-4010GSL, 6010SL, AX-300, AN-300, A-6100, An-180, AN-80, Tascam Series 70, Tascam Model 10 mixer |- || '''1973''' - 1230, 1250, 4010GSL, 6010GSL, 7010GSL, 7030GSL, 4070GSL, 3300-10, 3300-11, 3300-12, 2340, 3340S, TCA-43, AX-300, AN-300, Tascam Series 70, Tascam Model 10 mixer |- || '''1974''' - TASCAM acquired by Teac, Tascam Series 70, Tascam Model 10 mixer, Model 5 mixer, Teac 2340, 3340S |- || '''1975''' - A-2300 SX, A-2300SD, A-3300SX, A-3300SX 2T, A4100, A-4300SX, A-6300, A-7300, A-7300 2T, A-3340S, A-2340SX, Model 2 mixer with MB20 meter bridge, AX-20 mix down box |- || '''1976''' - Tascam 80-8 (used for Star Wars R2D2 sound), Model 1, Model 10B, Teac A-7300RX, A-3300 2T,A-2340, A-3340, Model 3 mixer, Model 5 mixer, Series 80, 40-4 |- || '''1977''' - Tascam DX-8, Model 25-2, Tascam 80-8 (Star Wars released), 25-2, A-2300SX, A-2300SR, A-2300SD, A-3300SX, A-3300SR A-3300SX 2T, A-4300SX, A-6300, A-6600, A-7300, A-7300 2T,A-3340S, A-2340SX, Model 2 mixer with MB20 meter bridge, Model 5 & Model 5EX, Studio 4000, 40-4, Model 3 mixer |- || '''1978''' - Model 2 mixer, model 15 mixer, Tascam 80-8 (used for Star Wars R2D2 sound ads), Model 5A mixer, 25-2, Studio 8000, A-2300SD, A-3300SX 2T, A-4300SX, A-3300S, A-2300S, A-3340S, A-2340S, A-7300, A-6300, A-6100 |- || '''1979''' - Tascam 90-16, Teac '''3440''', Model 144 Portatudio, 80-8, 40-4, 35-2, 5B & 5BX, Model1, |- || '''1980''' - Tasccam 85-16, A-'''3440''', A-3300SX 2T, A-2340SX, Model 2, MB20, A-6100MKII, GE-20 eq, 80-8, X-3, X-10R, ATR-700 built for Ampex, |- || '''1981''' - Tascam 80-16, System 20, Model 15SL mixer, 80-8, 40-4, Model 1 mixer, System 20, 22-2, 22-4, ATR-700 built for Ampex |- || '''1982''' - Tascam Model 15 SL, 80-8, Model 16 mixer, 85-16B, M-30, M-35 mixer, 32, 34, 38, 22-2, 22-4, Teac X-10, X-10R, X-20R, System 20, '''A-3440''', X-1000R, ATR-700 and ATR-800 built for Ampex |- || '''1983''' - Tascam 38, Tascam 58, , ATR-700 and ATR-800 built for Ampex, 22-2, 22-4, Series 50 52, 58, 80-16B, System 20, M50 mixer, M-15B mixer, M-16 mixer, Series 30 - M-30, M-35, 34, 38 |- || '''1984''' - Teac X-300, X-300R, X-700R, X-2000, X-2000R BL |- || '''1985''' - Tascam 388, MS-16, Teac X-300, X-300R, X-700R, X-2000, X-2000R |- || '''1986''' - Tascam 388, 32, '''34B''', 38, Series 40, 42B, 44, Teac X-300, X-300R, X-700R, X-2000, X-2000R |- || '''1987''' - Tascam 388, MS-16, ATR-60, ATR-80/24, '''Teac X-300''', X-300R, X-700R, X-2000, X-2000R |- || '''1988''' - Tascam Digital 24 track, 22-2, 32, 42B, M-600 mixer, ATR-60, ATR-60T, ATR-60-8, ATR-60-2N, ATR-60-2HS, ATR-60-16, Teac X-2000M(RO), X-2000(RO), X-2000R, X-300, X-300R |- || '''1989''' - Tascam MSR/24, MSR-16 |- || '''1990''' - Tascam MSR/24, MSR-16 |- || '''1991''' - Tascam M3000 mixer, MSR/24, MSR-16 |- || '''1992''' - Tascam BR-20, BR-20T |} fcfa68ebb9d09dde50a5327f5c990ffed481912a 6 136 2226 707 2018-08-15T11:32:19Z Pvdm 2 Pvdm uploaded a new version of [[File:Model-5a.jpg]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 395 2227 2225 2018-08-15T11:35:01Z Pvdm 2 Pvdm uploaded a new version of [[File:Samsie.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 397 2232 1332 2018-08-29T14:14:37Z Pvdm 2 wikitext text/x-wiki <pre> hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: WDC WD30EFRX-68EUZN0 Serial Number: WD-WCC4N0PFTP2N Firmware Revision: 82.00A82 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Supported: 9 8 7 6 5 Likely used: 9 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 5860533168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 2861588 MBytes device size with M = 1000*1000: 3000592 MBytes (3000 GB) cache/buffer size = unknown Nominal Media Rotation Rate: 5400 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test Media Card Pass-Through * General Purpose Logging feature set * 64-bit World wide name * URG for READ_STREAM[_DMA]_EXT * URG for WRITE_STREAM[_DMA]_EXT * IDLE_IMMEDIATE with UNLOAD * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * Idle-Unload when NCQ is active * NCQ priority information * unknown 76[15] DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) unknown 206[14] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 420min for SECURITY ERASE UNIT. 420min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee2b8f12459 NAA : 5 IEEE OUI : 0014ee Unique ID : 2b8f12459 Checksum: correct ------------------------------- hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: WDC WD30EFRX-68EUZN0 Serial Number: WD-WCC4N6PKUR2D Firmware Revision: 82.00A82 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Supported: 9 8 7 6 5 Likely used: 9 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 5860533168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 2861588 MBytes device size with M = 1000*1000: 3000592 MBytes (3000 GB) cache/buffer size = unknown Nominal Media Rotation Rate: 5400 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test Media Card Pass-Through * General Purpose Logging feature set * 64-bit World wide name * URG for READ_STREAM[_DMA]_EXT * URG for WRITE_STREAM[_DMA]_EXT * IDLE_IMMEDIATE with UNLOAD * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * Idle-Unload when NCQ is active * NCQ priority information * unknown 76[15] DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) unknown 206[14] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 448min for SECURITY ERASE UNIT. 448min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee2b8f20a8e NAA : 5 IEEE OUI : 0014ee Unique ID : 2b8f20a8e Checksum: correct f310bd660d3221e895dec6798ae85c9e4dc96b9e 0 545 2239 2018-08-29T14:21:51Z Pvdm 2 Created page with "<pre> lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Device..." wikitext text/x-wiki <pre> lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 5 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11) 619fa5cef0755bfe81e7209fef4c4234deddb375 0 544 2240 2237 2018-08-29T14:25:35Z Pvdm 2 wikitext text/x-wiki <pre>lsmod Module Size Used by fuse 106496 1 tcp_diag 16384 0 inet_diag 20480 1 tcp_diag xt_CHECKSUM 16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 3 nf_nat_masquerade_ipv4 16384 1 ipt_MASQUERADE iptable_nat 16384 1 nf_nat_ipv4 16384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 tun 32768 1 br_netfilter 24576 0 bridge 139264 1 br_netfilter stp 16384 1 bridge llc 16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter nf_log_ipv6 16384 20 xt_comment 16384 26 nf_log_ipv4 16384 20 nf_log_common 16384 2 nf_log_ipv4,nf_log_ipv6 xt_LOG 16384 40 xt_limit 16384 40 af_packet 45056 0 iscsi_ibft 16384 0 iscsi_boot_sysfs 20480 1 iscsi_ibft ip6t_REJECT 16384 3 nf_reject_ipv6 16384 1 ip6t_REJECT nf_conntrack_ipv6 20480 9 nf_defrag_ipv6 36864 1 nf_conntrack_ipv6 ipt_REJECT 16384 5 nf_reject_ipv4 16384 1 ipt_REJECT xt_pkttype 16384 7 xt_tcpudp 16384 84 iptable_filter 16384 1 ip6table_mangle 16384 0 nf_conntrack_netbios_ns 16384 0 nf_conntrack_broadcast 16384 1 nf_conntrack_netbios_ns nf_conntrack_ipv4 16384 12 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 ip_tables 24576 3 iptable_filter,iptable_mangle,iptable_nat xt_conntrack 16384 20 nf_conntrack 118784 8 nf_conntrack_netbios_ns,nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_broadcast,nf_conntrack_ipv4,nf_conntrack_ipv6 ip6table_filter 16384 1 ip6_tables 28672 2 ip6table_filter,ip6table_mangle x_tables 40960 17 xt_pkttype,ip6table_filter,ip6table_mangle,xt_comment,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables,ip6t_REJECT msr 16384 0 nct6775 61440 0 hwmon_vid 16384 1 nct6775 joydev 20480 0 hid_logitech_hidpp 20480 0 xfs 1085440 1 kvm_amd 86016 0 kvm 610304 1 kvm_amd raid456 147456 1 irqbypass 16384 1 kvm async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov libcrc32c 16384 2 xfs,raid456 crct10dif_pclmul 16384 0 async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov crc32_pclmul 16384 0 xor 20480 1 async_xor crc32c_intel 24576 1 async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov hid_logitech_dj 20480 0 ghash_clmulni_intel 16384 0 raid6_pq 118784 3 async_pq,raid456,async_raid6_recov md_mod 155648 2 raid456 drbg 28672 1 ansi_cprng 16384 0 usbhid 53248 0 snd_usb_audio 188416 0 snd_usbmidi_lib 36864 1 snd_usb_audio snd_hwdep 16384 1 snd_usb_audio snd_rawmidi 36864 1 snd_usbmidi_lib snd_seq_device 16384 1 snd_rawmidi snd_pcm 135168 1 snd_usb_audio aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw 16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper 16384 1 aesni_intel ablk_helper 16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper snd_timer 36864 1 snd_pcm snd 90112 7 snd_usb_audio,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_usbmidi_lib,snd_seq_device '''r8169 90112 0''' soundcore 16384 1 snd '''mii 16384 1 r8169''' i2c_piix4 24576 0 k10temp 16384 0 pcspkr 16384 0 shpchp 36864 0 acpi_cpufreq 20480 0 fjes 32768 0 video 45056 0 processor 49152 5 acpi_cpufreq button 16384 0 nfsd 348160 9 auth_rpcgss 65536 1 nfsd nfs_acl 16384 1 nfsd lockd 102400 1 nfsd grace 16384 2 nfsd,lockd sunrpc 364544 13 nfsd,auth_rpcgss,lockd,nfs_acl ext4 651264 3 crc16 16384 1 ext4 jbd2 118784 1 ext4 mbcache 16384 4 ext4 sr_mod 24576 0 cdrom 61440 1 sr_mod sd_mod 57344 11 amdkfd 143360 1 amd_iommu_v2 20480 1 amdkfd ohci_pci 16384 0 '''r8168 540672 0''' radeon 1597440 1 i2c_algo_bit 16384 1 radeon drm_kms_helper 167936 1 radeon syscopyarea 16384 1 drm_kms_helper ahci 40960 6 sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper libahci 36864 1 ahci ttm 110592 1 radeon ohci_hcd 53248 1 ohci_pci pata_atiixp 16384 2 ehci_pci 16384 0 xhci_pci 16384 0 ehci_hcd 81920 1 ehci_pci xhci_hcd 192512 1 xhci_pci usbcore 274432 9 snd_usb_audio,ohci_hcd,ohci_pci,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd,xhci_pci drm 397312 4 ttm,drm_kms_helper,radeon usb_common 16384 1 usbcore ata_generic 16384 0 pata_amd 20480 0 libata 274432 5 ahci,libahci,pata_amd,ata_generic,pata_atiixp sg 49152 0 dm_multipath 32768 0 dm_mod 131072 1 dm_multipath scsi_dh_rdac 20480 0 scsi_dh_emc 16384 0 scsi_dh_alua 20480 0 scsi_mod 253952 8 sg,scsi_dh_alua,scsi_dh_rdac,dm_multipath,scsi_dh_emc,libata,sd_mod,sr_mod autofs4 45056 2 </nowiki> 88228f499f326771fc0ae887e8012bdfd9870ca7 0 548 2264 2263 2018-09-21T07:24:26Z Pvdm 2 wikitext text/x-wiki == File permissions == One of the important things you can do to help secure your MediaWiki install, is ensure that the user you are running php as (often www-data if using debian) and the user you are running mysql as, does not have write access to any web accessible directory with php enabled. * On unix-like systems, you can do this by ensuring that the mediawiki directory/files are owned by someone other than your web server user (www-data) or mysql server user. Depending on how you installed MediaWiki this may already be the case, but if not can be accomplished by doing <code>chown -R <usernamehere> /path/to/MediaWiki/</code> where username is a user other than the webserver or mysql user (commonly you would use your own username provided mysql</> and php are not running as your username). * '''After doing that step, you may however need to change the owner of the image directory back to the php user,''' as uploaded files need to go there, so MediaWiki needs to be able to write there (e.g. <code>chown -R www-data /path/to/MediaWiki/images</code>). * Next you run <code>chmod -R go-w /path/to/MediaWiki</code> to remove write access from all other users besides the file owners. * After doing that step you may need to re-enable write access to the images directory. * Directories that MediaWiki needs write access to (such as $wgCacheDirectory if that feature is enabled) should be located outside of the web root. The exception being the images directory, which must be in the web root. * However, it is important to disable php in the images directory. The details on how to do this varies with webserver, but on apache it can sometimes be accomplished by using <code>php_flag engine off</code> in a .htaccess</> file. If you do accomplish this via a config file in the images directory itself, you should ensure the config file is not writable by the webserver. See the section below on upload security for more details. * Your LocalSettings.php file must be readable by the php user, however it should not be world readable, to prevent other processes from discovering your database password and other sensitive information. Like all MediaWiki files, the php user should not be able to write to LocalSettings.php. ==permissions== New install of MediaWiki 1.28 on Ubuntu 16.04. Permissions for /var/www/html set to 755, owned by me user:www-data. Did a Download from Git install, before and after doing composer install, the file and directory permissions are readable and writable but not executable for group. Should I set them to 755 manually? In your MediaWiki directory, the following SSH commands should work: find . -type f -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \; ==securing== The following picks up on a fresh working LAMP installation under Red Hat 7 or clone (CentOS 7, Scientific Linux 7, Orcale 7, etc). Set Selinux to permissive for the installation. setenforce 0 First get the Mediawiki version you want from https://releases.wikimedia.org/mediawiki/ , at time of writing latest is https://releases.wikimedia.org/mediawiki/1.27/mediawiki-1.27.0.tar.gz and unpack it in /var/www/html/w. Navigate to https://www.example.com/w and follow on-screen instructions to generate content used for LocalSettings.php. Create LocalSettings.php with vi /var/www/html/w/LocalSettings.php and paste content into file (<kbd>i</kbd> -> enter insert mode, <kbd>CTRL</kbd>+<kbd>SHIFT</kbd>+<kbd>v</kbd> to paste content, <kbd>ESC</kbd> -> to exit insert mode, <kbd>Z</kbd><kbd>Z</kbd> (twice letter Z) to save and exit vi). Now secure LocalSettings.php with chown root:apache /var/www/html/w/LocalSettings.php chmod 640 /var/www/html/w/LocalSettings.php Delete mw-config if it exists, since it is only used for first time setup of mediawiki. rm -rf /var/www/html/w/mw-config Enable use of .htaccess files by creating custom configuration file for Apache httpd. cat >> /etc/httpd/conf.d/custom.conf << EOF <Directory "/var/www/html/w"> AllowOverride All </Directory> EOF Now one should customize LocalSettings.php to one's taste. Here an overview of variables that can be customized: https://www.mediawiki.org/wiki/Manual:Configuration_settings Since we want to access our Mediawiki installation under https://www.example.com/wiki we need to set $wgArticlePath in LocalSettings.php. Just add the following line a the bottom of LocalSettings.php $wgArticlePath = "/wiki/$1"; and update /etc/httpd/conf.d/ssl.conf by adding one line. <VirtualHost _default_:443> Alias /wiki /var/www/html/w/index.php # <-- only add this line ===selinux=== Now finish securing the Mediawiki installation. This *may* be needed for Selinux, e.g. database on different server, etc. setsebool -P httpd_can_network_connect 1 setsebool -P httpd_can_network_connect_db 1 This *is* needed for Selinux to run Mediawiki setsebool -P httpd_builtin_scripting 1 setsebool -P httpd_execmem 1 Set userrights and special Selinux rights, so Apache httpd has read access, but other users beside root don't. chown -R root:apache /var/www/html/ find /var/www/html/w -type d -exec chmod 750 {} \; find /var/www/html/w -type f -exec chmod 640 {} \; Mediawiki writes to images and cache, so they need special write premissions. chown -R apache:apache /var/www/html/w/images chown -R apache:apache /var/www/html/w/cache semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/html/w/cache(/.*)?" semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/html/w/images(/.*)?" restorecon -R /var/www/html/w Found Selinux complaining about hugetlbfs, so add an exception. cd /var/log/audit grep hugetlbfs audit.log | audit2allow -M hugetlbfs semodule -i hugetlbfs.pp Now restart Apache httpd and set Selinux back to enforcing. setenforce 1 systemctl restart httpd Understandably this covers only the basics and Mediawiki offers thousands of ways to customize it further to one's taste and security needs. Don't forget to make regular backups. Further suggestions can be found here https://www.pozzo-balbi.com/help/Mediawiki . 0e7f81f3f77e7a36219124fe25ed29de4bd28589 0 20 2265 714 2018-09-22T07:57:28Z Pvdm 2 wikitext text/x-wiki *[[How to make Audacity work with ALSA]] *[[Normalize audio]] *[[Play audacity over network]] ab720709d297a4657e347feded8d3305d4a33774 0 549 2266 2018-09-22T07:59:30Z Pvdm 2 Created page with "=How to play Audacity over network using pulseaudio sound server= If you use pulse-audio as sound server, you can use <nowiki>module-native-protocol-tcp</nowiki> to accept tc..." wikitext text/x-wiki =How to play Audacity over network using pulseaudio sound server= If you use pulse-audio as sound server, you can use <nowiki>module-native-protocol-tcp</nowiki> to accept tcp connection from your remote machine. In the following example, I use an ssh tunnel to forward the audio request from remote machine to the local one. On the local machine, do something like: $ pactl load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 $ ssh -XC -R 9999:127.0.0.1:4713 pvdm@192.168.1.1 then on remote machine you can use: $ paplay -s 127.0.0.1:9999 soundfile.wav $ padsp -s 127.0.0.1:9999 audacity ADDED I discovered that auth-ip-acl does not accept localhost as a valid parameter, you have to use 127.0.0.1 (or whatever your machine uses localhost address). 3fcd120ef343779a7c07bad1a66e4f34978dbd80 0 550 2274 2273 2018-10-19T10:58:10Z Pvdm 2 wikitext text/x-wiki Startup options: <pre> --start-time=<integer> Start time The stream will start at this position (in seconds). --stop-time=<integer> Stop time The stream will stop at this position (in seconds). --run-time=<integer> Run time The stream will run this duration (in seconds). </pre> get around the problem by adding vlc://pause:9999 entries to playlist after the titles. <pre> #EXTM3U #EXTINF:350,Steely Dan - Babylon Sisters /data/audiophile/!!AA meeting okt 2018/01 - Babylon Sisters.flac vlc://pause:4 #EXTINF:461,Jeff Wayne - Forever Autumn /data/audiophile/!!AA meeting okt 2018/04 Jeff Wayne - Forever Autumn.flac vlc://pause:4 #EXTINF:311,Dire Straits - So Far Away /data/audiophile/!!AA meeting okt 2018/01 - So Far Away.flac vlc://pause:4 </pre> see: http://wiki.videolan.org/VLC_command-line_help a5a3d34d01e4e3ffbe0c8d9a7dd90727654b03fa 0 489 2285 2284 2018-10-28T15:14:51Z Pvdm 2 /* convert bitrate */ wikitext text/x-wiki =THX-like sound= play -q -n synth sq F2 sq C3 remix - fade 0 5 .1 norm -4 bend 0.5,2477,3 fade 0 5 0.8 =white noise= play -n -c1 synth whitenoise lowpass -1 120 lowpass -1 120 lowpass -1 120 gain +14 =play keys piano asdfghj= n=CDEFGAB;l=asdfghj;while read -n1 k;do x=$(tr $l $n<<<$k);play -qn synth pl ${x}3 fade 0 .7 & done =warble sound= play -n synth sq C trim 0 4 vol 0.2 chorus 1 1 21 1 4 10 -s bend 0,2400,4 fade 0.1 4 2 =convert bitrate= sox "02 It's Time.flac" -b 16 -r 44.1k "02 It's Time 44100.flac" converts from 48000 to 44100 09115a9c6b74c53fd38cba748dffca428a146634 0 555 2306 2018-12-08T10:11:58Z Pvdm 2 Created page with " {| cellspacing="0" border="0"<colgroup width="84"></colgroup><colgroup width="98"></colgroup><colgroup width="67"></colgroup><colgroup width="93"></colgroup><colgroup width="..." wikitext text/x-wiki {| cellspacing="0" border="0"<colgroup width="84"></colgroup><colgroup width="98"></colgroup><colgroup width="67"></colgroup><colgroup width="93"></colgroup><colgroup width="102"></colgroup><colgroup width="86"></colgroup><colgroup span="2" width="67"></colgroup><colgroup width="86"></colgroup><colgroup width="111"></colgroup><colgroup width="67"></colgroup><colgroup width="84"></colgroup><colgroup width="86"></colgroup><colgroup width="67"></colgroup><colgroup width="74"></colgroup><colgroup width="84"></colgroup><colgroup width="156"></colgroup><colgroup width="67"></colgroup><colgroup width="73"></colgroup><colgroup width="89"></colgroup> | height="85" align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | De-Equalizer | align="left" | Digital Drive Signal Processor | align="left" | Error Correction Codec | align="left" | Tape Format and Error Correction? | align="left" | Drive Processor | align="left" | Subband Codec | align="left" | Subband Filter | align="left" | Stereo Filter and Codec | align="left" | Adaptive Allocation and Scaling | align="left" | Digital Audio Interface | align="left" | | align="left" | Digital to Analog Converter | align="left" | Analog to Digital Converter | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | Head (A+P+R) | align="left" | Bits | align="left" | Read | align="left" | Write | align="left" | DEQ *2 | align="left" | DDSP | align="left" | ERCO | align="left" | TFE | align="left" | DRP/SPD1 | align="left" | SBC | align="left" | SBF | align="left" | SFC | align="left" | ADAS | align="left" | DAI/DAIO | align="left" | Dig Filter | align="left" | DAC | align="left" | ADC | align="left" | ADC/DAC | align="left" | Dolby |- | height="17" align="left" | DCC900 | align="left" | 2+9+9 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | TDA1317 | align="left" | TDA1316T/N-T | align="left" | SAA2051 | align="left" | SAA2041 | align="left" | SAA2031 | align="left" | n/a | align="left" | n/a | align="left" | SAA2021 | align="left" | 2x SAA2001 | align="left" | n/a | align="left" | SAA2011 | align="left" | M51581FS | align="left" | SM5840FS | align="left" | SAA7350 | align="left" | AK5326 | align="left" | n/a | align="left" | CXA1331 |- | height="17" align="left" | RS-DC10 | align="left" | 2+9+9 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | TDA1317 | align="left" | TDA1316T | align="left" | SAA2051 | align="left" | SAA2041 | align="left" | SAA2031 | align="left" | n/a | align="left" | n/a | align="left" | SAA2021 | align="left" | 2x SAA2001 | align="left" | n/a | align="left" | SAA2011 | align="left" | M51581FP | align="left" | SM5840FS | align="left" | SAA7350 | align="left" | AK5326 | align="left" | n/a | align="left" | CXA1331 |- | height="17" align="left" | DD82/92 | align="left" | 2+9+9 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | TDA1317 | align="left" | TDA1316T | align="left" | SAA2051 | align="left" | SAA2041 | align="left" | SAA2031 | align="left" | n/a | align="left" | n/a | align="left" | SAA2021 | align="left" | 2x SAA2001 | align="left" | n/a | align="left" | SAA2011 | align="left" | M51581FP | align="left" | SM5840FS | align="left" | SAA7350+TDA1547 *da | align="left" | AK5326 | align="left" | n/a | align="left" | CXA1331 |- | height="17" align="left" | DCC600 | align="left" | 2+9+9 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | TDA1317 | align="left" | TDA1316T | align="left" | SAA2051 | align="left" | SAA2041 | align="left" | SAA2031 | align="left" | n/a | align="left" | n/a | align="left" | SAA2021 | align="left" | 2x SAA2001 | align="left" | n/a | align="left" | SAA2011 | align="left" | M51581P | align="left" | *df | align="left" | SAA7321 | align="left" | AK5339 | align="left" | n/a | align="left" | CXA1331 |- | height="17" align="left" | DCC300/380 | align="left" | 2+9+9 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | TDA1317 | align="left" | TDA1316T | align="left" | SAA2051 | align="left" | SAA2041 | align="left" | SAA2031 | align="left" | n/a | align="left" | n/a | align="left" | SAA2021 | align="left" | 2x SAA2001 | align="left" | n/a | align="left" | SAA2011 | align="left" | M51581FP | align="left" | *df | align="left" | SAA7323 | align="left" | AK5339 | align="left" | n/a | align="left" | CXA1331? |- | height="17" align="left" | DCC91/450 | align="left" | 2+9+9 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | TDA1317 | align="left" | TDA1316T | align="left" | SAA2051 | align="left" | SAA2041 | align="left" | SAA2031 | align="left" | n/a | align="left" | n/a | align="left" | SAA2021 | align="left" | 2xSAA2001 | align="left" | n/a | align="left" | SAA2011 | align="left" | M51581FP | align="left" | *df | align="left" | SAA7323 | align="left" | AK5339 | align="left" | n/a | align="left" | CXA1331 |- | height="17" align="left" | DCC130 | align="left" | 0+18+0 | align="right" sdval="16" sdnum="1043;" | 16 | align="left" | 2xTDA1318H | align="left" | *p | align="left" | SAA2032GP | align="left" | *t | align="left" | *t | align="left" | SAA2022GP | align="left" | n/a | align="left" | *f | align="left" | *f | align="left" | SAA2002GP | align="left" | *p | align="left" | M51581GP | align="left" | SM5881SET | align="left" | UPD63200GSE2 | align="left" | *p | align="left" | n/a | align="left" | BA1106FST2 |- | height="17" align="left" | DCC134 | align="left" | 0+18+0 | align="right" sdval="18" sdnum="1043;" | 18 | align="left" | TDA1380 | align="left" | *p | align="left" | *d | align="left" | *d | align="left" | *d | align="left" | n/a | align="left" | SAA3323 | align="left" | *f | align="left" | *f | align="left" | SAA2003 | align="left" | *p | align="left" | *p *i | align="left" | SM5881S | align="left" | TDA1313T | align="left" | *p | align="left" | n/a | align="left" | BA1106FS |- | height="17" align="left" | DCC170 | align="left" | 4+18+18 | align="right" sdval="18" sdnum="1043;" | 18 | align="left" | TDA1380 | align="left" | TDA1381 | align="left" | *d | align="left" | *d | align="left" | *d | align="left" | n/a | align="left" | SAA3323 | align="left" | *f | align="left" | *f | align="left" | SAA2003 | align="left" | SAA2013 | align="left" | TDA1315 | align="left" | *df | align="left" | *ad | align="left" | *ad | align="left" | TDA1309H | align="left" | BA1106FS |- | height="17" align="left" | DCC175 | align="left" | 4+18+18 | align="right" sdval="18" sdnum="1043;" | 18 | align="left" | TDA1380 | align="left" | TDA1381 | align="left" | *d | align="left" | *d | align="left" | *d | align="left" | n/a | align="left" | SAA3323 | align="left" | *f | align="left" | *f | align="left" | SAA2003 | align="left" | SAA2013 | align="left" | TDA1315 | align="left" | *df | align="left" | *ad | align="left" | *ad | align="left" | TDA1309H | align="left" | BA1106FS |- | height="17" align="left" | DCC730 | align="left" | 2+9+9 | align="right" sdval="18" sdnum="1043;" | 18 | align="left" | TDA1317 | align="left" | TDA1319 | align="left" | *d | align="left" | *d | align="left" | *d | align="left" | n/a | align="left" | SAA3023 | align="left" | *f | align="left" | *f | align="left" | SAA2003 | align="left" | SAA2013 | align="left" | TDA1315 | align="left" | *df | align="left" | TDA1305T | align="left" | SAA7366 | align="left" | n/a | align="left" | CXA1331S |- | height="17" align="left" | DCC951 | align="left" | 2+9+9 | align="right" sdval="18" sdnum="1043;" | 18 | align="left" | TDA1317 | align="left" | TDA1319 | align="left" | *d | align="left" | *d | align="left" | *d | align="left" | n/a | align="left" | SAA3023 | align="left" | *f | align="left" | *f | align="left" | SAA2003 | align="left" | SAA2013 | align="left" | TDA1315 | align="left" | *df | align="left" | TDA1305T | align="left" | SAA7366 | align="left" | n/a | align="left" | CXA1331S |- | height="17" align="left" | RS-DC8 | align="left" | 2+9+9 | align="left" | ? | align="left" | AN7631FHPV | align="left" | AN7639SBE2V | align="left" | *s | align="left" | *s | align="left" | *s | align="left" | n/a | align="left" | MN66703 | align="left" | MN66702 | align="left" | MN66701 | align="left" | n/a | align="left" | *m | align="left" | M65812FP | align="left" | *df | align="left" | MN64782 | align="left" | MN6463 | align="left" | n/a | align="left" | AN7374S-E2 |- | height="17" align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *p | align="left" | Not needed, this device is a player only | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *d | align="left" | Functionality integrated in Drive Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *t | align="left" | Functionality integrated in TFE | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *s | align="left" | Matsushita integrated functionality into "SPDI" | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *m | align="left" | Matsushita integrated functionality into "SBC" | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *f | align="left" | SBC and SBF replaced by SFC? | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *i | align="left" | No digital I/O, analog I/O only | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *df | align="left" | Digital Filter not needed for DAC in this device | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *ad | align="left" | ADC and DAC integrated into one chip | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | *da | align="left" | The TDA1547 works together with the SAA7350 | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | AK5326 | align="left" | Analog Digital Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | AK5339 | align="left" | Analog Digital Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | AN7374S-E2 | align="left" | Dolby Playback Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | AN7631FHPV | align="left" | Read Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | AN7639SBE2V | align="left" | Write Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | BA1106FS | align="left" | Dolby Playback Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | BA1106FST2 | align="left" | Dolby Playback Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | CX1331 | align="left" | Dolby Playback Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | CX1331S | align="left" | Dolby Playback Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | M51581FP | align="left" | Digital Audio Interface | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | M51581FS | align="left" | Digital Audio Interface | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | M51581GP | align="left" | Digital Audio Interface | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | M51581P | align="left" | Digital Audio Interface | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | M65812FP | align="left" | Digital Audio Interface | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | MN6463 | align="left" | Analog Digital Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | MN64782 | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | MN66701 | align="left" | Subband Filter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | MN66702 | align="left" | Subband Codec | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | MN66703 | align="left" | Speed Controller | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1305T | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1309H | align="left" | ADC/DAC | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1313T | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1315 | align="left" | Digital Audio Interface | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1316T | align="left" | Write Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1317 | align="left" | Read Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1318H | align="left" | Read Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1319 | align="left" | Write Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1380 | align="left" | Read Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1381 | align="left" | Write Amplifier | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | TDA1547 | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2001 | align="left" | Subband Filter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2002GP | align="left" | Subband Filter and Codec | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2003 | align="left" | Stereo Filter and Codec | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2011 | align="left" | Adaptive Allocation and Scaling | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2013 | align="left" | Adaptive Allocation and Scaling | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2021 | align="left" | Subband Codec | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2022 | align="left" | Tape Format and Error Correction | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2031 | align="left" | Error Correction Codec | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2032GP | align="left" | De-equalizer | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2041 | align="left" | Digital Drive Signal Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA2051 | align="left" | De-equalizer | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA3023 | align="left" | Drive Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA3323 | align="left" | Drive Processor | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA7321 | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA7323 | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA7350 | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SAA7366 | align="left" | Analog Digital Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SM5840FS | align="left" | Digital Filter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SM5881S | align="left" | Digital Filter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | SM5881SET | align="left" | Digital Filter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |- | height="17" align="left" | | align="left" | UPD63200GSE2 | align="left" | Digital Analog Converter | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | | align="left" | |} 9fd7ee44e2ee5dd5d5114cb01d58efe7c23b401f 0 556 2314 2313 2018-12-22T09:56:07Z Pvdm 2 wikitext text/x-wiki <pre> The latest product upgrades, increase optical output! ! ! This product USB direct power supply, Input: USB input, print port and Android interface, input easily linked computer or mobile phone Output: output optical! Coaxial! Linear audio! Headphone output! Easily drive 300 European and American headphones A finished board, finished machine optional! Black or silver white shell! CNC high-precision machining, pure aluminum chassis structure, 6631 combined with multiple version optimization and improvement, sound sophistication beyond XMOS, Naiting, not irritable! Small exquisite children! ! Each board test OK delivery, using anti-static packaging .Windows10 automatic identification, you need to drive can contact me Support coaxial SPDIF '''output''' Support I2S output can be external decoder Internal includes ES9023 own decoded audio output Can connect mobile OTG, recommended player download address http://www.hiby.cd/ Compatible more stable. By professional PCB full posts, precision parts design. All posts using active low temperature Support millet box, the other boxes are not all tested, compatible with Apple, PC Computer WindowXP / 7/8/10 Float crystal vibration, high-quality optical fiber to ensure 192K transmission performance. Support 24bit / 44.1K, 48K, 88.2K, 96K, 176.4K, 192K, Usb audio input and up to 32BIT 192K audio input onboard three Panasonic gold capacitors, high-precision active crystal oscillator, the latest version of the optimized wiring, better indicators! Output 1: Audio Input with ES9023 High-Precision Decode IC with Internal Drive Circuit High Thrust Output 2: I2S output, can be connected to other DA devices Output 3: SPDIF output! That is a coaxial output and optical output Brand Name:Olive Leaf D/A Converter:CM6631A Model Number: Sound Card USB to I2S DSD Sampling Frequencies:None Outputs:RCA,3.5 mm Material:Metal PCM Word Length:24-bit,32-bit PCM Sampling Frequencies:192 kHz USB Compatibility:IOS,Windows 8,Windows 10,Windows 7 Inputs:USB Type-B,USB Type-A Bluetooth:No Type:Portable </pre> f133e7f7e85942c55b897223757d941e7b323633 6 558 2334 2019-01-27T08:18:01Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 559 2340 2019-01-27T09:28:41Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 531 2341 2339 2019-01-27T09:31:14Z Pvdm 2 /* Technology */ wikitext text/x-wiki Peter W. Mitchell: The public debut of Philips's digital compact cassette (DCC) was the biggest event at the 1991 CES in Las Vegas, which began with a large press conference that drew a crowd of about 200 audio journalists. Philips executives laid out the logic underlying the DCC's design, how it will be marketed, and the technical principles of its operation. Except for an awkward moment when a cassette-well door on a prototype DCC deck refused to open, the presentation was persuasive and the free buffet supper—featuring sinfully delicious lamb chops—was the best I've tasted at any CES press conference in years. During the next two days audio writers were invited upstairs in smaller groups of 10 to 20, to ask questions and hear the system in a hotel-room setting. There are three stories in the DCC debut: what it sounded like, how it works, and how its performance was refined. Of these, the last proved to be the most surprising. =Sound= A DCC recording uses only a fourth as many bits per second as a CD thorugh bit-rate reduction (footnote 1). Since the DCC is intended to be a mass-market product, and since the CD has already been accepted as the mass-market standard for sound quality, Philips set up a demonstration whose aim was to illustrate that the DCC provides CD-quality sound in a smaller and conveniently home-recordable package. For each group of a dozen or so audio writers, Philips played a comparison of CD vs DCC sound through a system of good but not ultimate quality, a system that might retail for between $5000 and $10,000. The signal from the CD player was fed to a preamp and also to a prototype DCC encoder/decoder. By the time the system goes into production the DCC processing circuits will have been shrunk to a handful of ICs that will fit within a standard-size cassette deck; at present the circuits fill a cube about 24" on each side. The DCC signal was encoded for recording and then decoded for playback, but was not actually recorded on tape. (In principle, that should not affect the comparison, since the system has enough error-correction capacity to handle normal tape imperfections.) The output from the DCC unit was precisely matched in level to that from the CD, and a switch enabled an A/B comparison between the CD "original" and the encoded/decoded DCC "copy." How did it sound? "It was not obviously flawed." This is an audiophile reviewer's cover-your-butt way of saying that he didn't hear any difference but doesn't want to go out on a limb and say that the sound was identical, because he doesn't want fellow reviewers to think him cloth-eared. In fact, most of the people I spoke with afterward heard no difference in most of the comparisons. Some of the invited writers challenged the system with their favorite CDs of music or test signals. Ironically, as I will explain later, two widely used test signals, pink noise and pure sinewave tones, are very useful for detecting faults in analog and conventional (linear PCM) digital products but are especially easy for the DCC to handle. The most challenging test may be simple music, a signal that has energy at several frequencies but also has empty spaces in the spectrum, in which the ear might hear low-level artifacts. One writer felt that the DCC's noise floor was not quite as low as that of an optimally dithered CD (notably the low-level glide tone on the CBS test disc). Others felt that the DCC sounded slightly brighter and coarser than the CD. However, when the A/B switch was operated there was a switching transient (a short noise burst) and an audible time offset caused by slight delays in DCC encoding which might have produced an illusion of a sonic difference even where there was none. I remained after a group demo and was treated to an additional private A/B comparison in which I selected CDs that I thought would be particularly revealing, sat in the optimum stereo-center seat, and operated the A/B switch myself. I soon became convinced that I heard a slight difference (B was brighter than A). Then, after I deliberately lost track of the switching order, I found it easy to persuade myself that A sounded slightly brighter than B—indicating that my perceptions were indeed being affected by the switching transient. Of course, conditions were not conducive to the most critical evaluation. The all-Philips playback system (Philips electronics and four-way Philips speakers) did not seem as transparent and revealing of subtle differences as, for example, a system based on Apogee Stage speakers. And while the Philips personnel thoughtfully switched off the room's noisy airconditioning unit during the comparisons, the ambient noise level was still higher than in most homes. So I tried to think of a way to enhance the audibility of any subtle flaw the DCC might have. Two possibilities immediately came to mind. First, since the DCC uses only a fourth as many bits as the CD, its handling of low-level hall ambience might be impaired, especially if the compressed digital bitstream is not optimally dithered to minimize quantizing distortion. Second, one historically popular way of boosting the apparent information-carrying capacity of a limited channel is to use matrix encoding. For example, stereo FM radio produces an illusion of decent sound by combining mono FM (an L+R signal having inherently wide dynamic range and fairly low distortion) with an L–R subcarrier that has high distortion and limited range. The poor quality of the L–R subcarrier is often masked by the much louder L+R portion of the composite signal. Similarly, the analog LP began as a low-distortion, wide-range medium that used purely lateral modulation for its mono (L+R) information; then it was converted to stereo by adding an L–R stereo "difference" signal as a vertical modulation that has much higher distortion and a very limited dynamic range. This is mathematically equivalent to modulating the two walls of the LP groove at 45° with separate left and right signals. But the vertical/horizontal picture leads to a clearer understanding of the medium's limits. In the early days of the stereo LP there were great debates in hi-fi magazines about whether the improved perspective of stereo was valuable enough to offset the new distortions (pinch effect, etc.) that became a problem when the stylus had to detect deliberate vertical modulation. Historically, one of the most important aspects of an LP mastering engineer's job was to artfully limit the vertical excursion of the stylus in ways that didn't obviously compromise the sound. It was crucially important to make sure that the cutting stylus could never rise completely out of the lacquer (producing a discontinuous groove) or penetrate all the way through to the bottom of the acetate and scrape the glass or metal backing plate that the lacquer was coated on. The stereo LP, even more than stereo FM, succeeded because most of the time the L+R (horizontal) portion of the signal is much louder than, and effectively masks the flaws of, the L–R (vertical) stereo difference portion of the composite modulation. There's a very easy way to discover how well any audio medium handles low-level ambience, and also to learn whether it uses matrix encoding to mask its limitations: listen to the L–R portion of the signal separately, without the louder L+R portion. In this mode one can also listen for variations in the level or timbre of the L–R signal, which may be caused by the two channels going partly or wholly out of phase at high frequencies—a common fault in phono pickups, analog tapes (both cassette and quarter-track open-reel), and early CD players. In stereo playback this fault causes problems in soundstage imaging. In FM broadcasting it causes severe dulling of the highs (and, in severe cases, comb-filter coloration) when a stereo broadcast is heard in mono. Anyone who still has the classic Apt/Holman preamp can do this test easily: just rotate the Mode knob from Stereo to the L–R position. To achieve an equivalent result, I asked the Philips folks to disconnect the speaker wires at the back of the amplifier and connect the wires from one speaker to the left and right "hot" terminals, so that the speaker would reproduce just the L–R portion of the stereo signal. After a brief hesitation while they wondered if this connection might risk the amplifier's stability, they proceeded to do it. I was impressed, and a little surprised, by this cooperative attitude. It suggested that although they hadn't tried this test themselves, the Philips people were so confident of the DCC's sound quality that they didn't expect to be embarrassed. Their implied vote of confidence was doubly impressive because by the time I suggested this rewiring of the demo system, the next group of audio writers had arrived—and when they heard about the proposal they were as eager as I to hear the result. This group included Michael Riggs, now an editor at Stereo Review, and Ken Pohlmann, whose informed writings on digital audio are published in several big-circulation consumer and pro audio magazines. If the L–R test revealed a flaw in the DCC, the bad news would be published far and wide. Not to worry; the DCC passed with flying colors. To challenge it, I chose a nicely recorded Philips CD of Schubert songs for solo voice and piano. In the L–R mode the soprano voice, imaged precisely in the center of the stereo stage, was substantially canceled out, dropping in level by about 20dB. The direct sound of the piano also declined in level. With most of the low-frequency and midrange body of tone removed, what remained were high-frequency harmonics and all of the recorded hall ambience, including the delicate tail end of the reverberation. Recall that the DCC encoder was still handling the full stereo signal; the L–R subtraction took place only at the amplifier output. As we listened alternately to the CD and to the DCC "copy," even the L–R mode did not reveal any clear difference in timbre, ambience, or low-level resolution. Of course, a CD is not itself an absolute standard of sound quality, especially since most available CDs were recorded through the Sony PCM-1610 or 1630—digital processors with sonic limitations of their own. At the show the Philips folks mentioned that the next phase in refining the DCC encoder would involve comparisons with new CDs that were recorded with "20-bit equivalent" oversampling delta-sigma A/D converters—for instance, the UltraAnalog (formerly dbx) converter used by Chesky (footnote 2) and the Bitstream A/D that is now used in some Japanese studios. To sum up: the DCC, while using only a fourth as many bits as the CD, successfully duplicates average-quality CD sound. If it isn't an exact match, the disparity is about on the same scale as the differences among CD players. We don't know yet whether it may prove unsatisfactory by high-end audiophile standards (footnote 3), or whether it will sound as good as the very best R-DATs. But it is better than it needs to be for the mass market—and is light-years ahead of the analog cassette that it is destined to replace. =Technology= The impetus to develop DCC came not from a technical breakthrough but from a marketing problem. When Japanese manufacturers launched the R-DAT format five years ago, they proclaimed it the digital successor to the analog cassette, just as the CD is supplanting the LP. An interesting idea, but is it likely? At the high end of the home recording market, and among hi-fi hobbyists who are actively involved in taping, the answer is yes. It's worth remembering that Japanese hi-fi gear is developed first for the domestic market and is then sold to the rest of the world. Japanese audio hobbyists love tape recording. (Open-reel tape machines continued to flourish in Japan long after they died in every other market.) And because Japanese hi-fi buffs like to assemble their own compilations of favorite music, and to fool around with sound effects, the first DAT recorders were designed to facilitate easy digital dubbing from CDs. In early R-DAT brochures the new format was presented as the heart of a complete living-room digital studio for every hi-fi enthusiast. Of course, when major record companies understood this, they launched a legal and political war against DAT that is still going on. Even assuming that R-DAT might someday capture the entire market for living-room tape decks, is that where the analog cassette market is? Not at all. This year Americans will buy more than 30 million cassette mechanisms, but only 3 million will be AC-powered living-room decks. The other 90% operate in motion: headphone portables, radio/cassette boomboxes, and car stereos. The majority of these are play-only; even those equipped for recording (eg, boomboxes and some headphone portables) are used mainly to play prerecorded tapes. In the US there are as many cassette mechanisms as people. The average household has three. Worldwide, a billion cassette mechanisms are in use. This year people will buy 180 million new machines and a billion prerecorded music cassettes (fig.1). Another billion and a half blank cassettes are sold annually, many for non-musical applications (telephone answering machines, taping college lectures, journalist interviews, talking books for the blind, et al). [[File:1.jpg|right|400px|Fig.1 Worldwide recorded and blank media market, 1988 (© Bureau Contekst).]] Philips invented the cassette format in 1963 and may be more aware than anyone else of its worldwide dominance as the leading carrier of recorded music. Looking at the numbers, Philips concluded that regardless of how successful the R-DAT might be among hi-fi hobbyists and living-room component systems, these account for only a tiny share of the market. There is no possibility that R-DAT could be the true digital successor to the analog cassette. It faces two fundamental obstacles: cost and software. Sony and Panasonic have done an impressive job of shrinking the price of DAT recorders from $2000 to $800. But how much lower can they go? A DAT mechanism is a miniature helical-scan VCR, with many precision parts in exacting alignment. If mass-production is the key to getting the price down, consider camcorders; they sell in the millions and still cost $500 to $1000 apiece. Yet CD players sell for as little as $99, while analog cassette mechanisms add less than $50 (often only $20) to the retail price of a product. My teenage niece has a $180 boombox that contains AM/FM radio, cassette, and a CD player that proved surprisingly competent when I connected its Line outputs to my brother's stereo component system. Could R-DAT conceivably have any future in this application, or in $40 headphone portables? Not a chance. As for software, copying discs onto tape is OK for hobbyists, but most people don't want to bother. They just want to buy music in a convenient package and enjoy it. There are tens of thousands of software titles available on analog cassette but only a few hundred on DAT. Sony recently announced plans to double the production capacity for prerecorded DAT at its Indiana factory. But that will still be mainly for Sony Classics and a few independent labels that want to produce DAT recordings for sale. Sony hasn't even managed to persuade the pop-music division of CBS Records (which it owns) to release DAT versions of Michael Jackson and Bruce Springsteen hits, much less the other large record companies (RCA, Warner, Arista, et al) that remain united in their opposition to DAT. Even if record companies accept DAT, recordings are duplicated by dubbing in real time onto racks of Sony DAT recorders, a slow and costly process. If enough demand developed, they could adopt Sony's $100,000 Sprinter, a high-speed duplicator that uses a magnetic "contact printing" process to transfer the magnetic pattern from a master tape to DAT duplicates. Still, while CDs now cost only a buck apiece to press, blank DAT cassettes cost about $5 in large quantities. Each DAT is a miniature videocassette, with a hinged door and a dozen internal parts, and the tape is a metal-powder formulation that is expensive to manufacture. The bottom line is that prerecorded DATs (if record companies were willing to produce them) would always cost substantially more than the equivalent CD. That's enough to limit their appeal and probably rules out R-DAT as the digital successor to the analog cassette. Philips concluded that the digital replacement for the analog cassette would have to be cheap enough to be a true mass-market product, be amenable to economical high-speed duplication, be supported by major record companies, and be readily adaptable to various physical forms (headphone portables, slot-load car players, and AC-powered home decks). So, rather than designing new mechanisms from the ground up, Philips decided to base the design of the DCC on analog cassette mechanisms that manufacturers around the world already produce in vast quantities at very low cost—from the $20 headphone portable made of plastic parts to the slot-load car player and the high-performance dual-capstan home deck. Many analog cassette mechanisms can be converted to DCC use by substituting a different head and adding a few small parts. The DCC cassette has the same exterior dimensions as the analog cassette, runs at the same 1 7/8ips tape speed, and has the same 90-minute running time (45 minutes per side). 120-minute tapes will also be produced, mainly to offer home recordists the same 2-hour capacity as R-DAT. But home recording is a relatively minor part of the product concept. More importantly, DCC cassettes have the same playing time as the CD (80-plus minutes), so prerecorded DCC tapes can be mass-produced from the same masters that CDs are cut from. As a bonus, the DCC offers the mass market a painless transition to the digital age: DCC machines will also play the dozens of analog cassettes that every home already possesses. (Compatibility and worldwide standards have always been high priorities at Philips.) The idea is that when your present cassette machine wears out and you go to buy a new one, you'll be tempted to upgrade to a DCC machine that will play all your old tapes and also provide CD-quality sound from new tapes. The analog playback will include Dolby-B since that is the world standard for prerecorded cassettes. Other manufacturers may include Dolby-S decoding, but Philips is reluctant because Type S is not a major factor in the prerecorded cassette market. (That may change by the time DCC decks arrive in 1992. Two large US tape duplicators recently converted their machines to Dolby-S encoding, which is said to be playback-compatible with Dolby-B.) Of course, there are important differences between analog and digital cassettes. Analog cassettes have a bulge along one edge to accept the heads; DCC cassettes are uniformly slim, so it is easy to carry several in a shirt pocket. Analog cassettes are symmetrical, since in many machines you flip the cassette over to access the Side B tracks. All DCC machines will use dual-capstan auto-reverse mechanisms, so the DCC cassette is never turned over. It has reel hubs and access holes only on the bottom; the flat top face is covered by a big label. A standard DCC machine will record and play digital tapes but won't record analog cassettes; it is playback-only. Reason: it is bidirectional, and adding dual erase and record heads for both directions would be expensive for a capability that few people would use. For those who still want to record analog cassettes (for friends, or to play in the car), Philips suggested that the most cost-effective solution would be a dual-well dubbing deck, DCC in one well and analog record/play in the other. Several years ago, when Apple introduced the first Macintosh computers, Steve Jobs began a presentation to the Boston Computer Society by tossing a handful of then-new 3.5" mini-floppy disks into the audience. Computer buffs, familiar with the vulnerability of conventional floppies, were startled and impressed by this cavalier behavior—especially when Jobs demonstrated that the mini-disk didn't need a protective envelope but could be carried bare in a shirt pocket. The plastic disk housing contains a sliding shutter that seals the case shut when not in use, protecting the disk from fingerprints and dust. Philips borrowed the same great idea for the DCC. Unlike analog cassettes, which are open along one edge and vulnerable, the digital cassette has a sliding metal shutter that protects the tape when it's not in the machine—forever eliminating awkward and easily broken "jewel box" carriers. Prerecorded DCC tapes will come in a transparent sleeve with program notes, but away from the living room you'll carry only the self-protected cassette. This fumble-free convenience is enough to make DCC the digital medium "for the rest of us." The sliding shutter doesn't add much to the cost of the DCC cassette; I paid only 39 cents for the 3.5" disks I use in my computer. According to Philips, the metal-powder tape required for R-DAT is costly, not amenable to conventional high-speed duplication, and unstable at the high temperatures that may occur in a closed car on a summer day. So the DCC was designed from the ground up to use low-cost tape, specifically video-format chromium dioxide, which is produced in vast quantities for VCRs. A Philips spokesman mentioned that with CrO2 tape and a housing that is not much more complex than an analog cassette, blank DCC cassettes may be priced only slightly higher than premium-grade analog tapes, around $5. (For comparison, blank R-DATs cost $8 to $15 at retail.) CrO2 tape can reliably record wavelengths as short as one micron (1;um or one-thousandth of a millimeter). At a tape speed of 4.75cm/s, this is equivalent to a maximum frequency of 47.5kHz. Since each cycle corresponds to two bits (a 1 followed by a 0), the corresponding data rate per track is 95,000 bits per second (bps). By recording on eight narrow tracks, the DCC records a total of about 760,000bps. About half (384,000bps) are audio data; the rest are used for error-correction coding. For comparison, the data rate in the CD is 1,408,000bps (44,000 samples/s x 16 bits/sample x 2 channels). Thus the data rate in the DCC is about one-fourth that of the CD. Since the sampling rate is the same, the DCC records an average of only four bits per sample. Low-level noise is added to "dither" the signal and thereby minimize any quantizing distortion. In addition to the eight tracks of digital data, a ninth track will contain subcodes, timing codes, a table of contents, and (optionally) up to 400 characters per second of text, which may be shown either on a built-in display or a separate video screen. The text could be used for song lyrics, program notes (synchronized with the music), multilingual opera librettos, background stories about the recording sessions, etc. Philips proposed a similar text display nine years ago for the CD, but the idea was ignored by record companies and most manufacturers, perhaps because it would require extra work to prepare the text for encoding with the signal when the master recording is cut. (Most CDs don't even have indexing of the sections of a symphonic movement, which takes relatively little effort to implement.) By monitoring the subcode track during fast-wind, a DCC player can cue quickly to the beginning of a song, display timings, play songs in any order, and generally provide the same operating conveniences as a CD or R-DAT. Cueing to another song may require a few seconds, as with R-DAT, instead of the near-instant cueing that CD provides. Since all DCC tapes will be recorded in auto-reverse format, the last song on Side B will be in the same section of tape as the first song on Side A, requiring only an auto-reverse maneuver (reverse the direction of tape motion and rotate the head 180°) to access it. If you're making your own recordings you'll have to plan ahead so that the automatic reverse at the end of the tape won't leave a two-second gap in the middle of a movement. (In this respect R-DAT is superior, with up to two hours of continuous, uninterrupted recording time.) The DCC combo head has gaps for the nine digital tracks in its upper half, plus two gaps for analog tracks in its lower half. When recording or playing Side B, the head is flipped to place the digital gaps on the bottom (fig.2). When you load an analog cassette, sensing pins automatically flip the head to put the analog gaps on top for side A. (Incidentally, since DCC tapes don't turn over, Philips wants to call the two tape directions the A and B "sectors" rather than "sides.") [[File:DCC-kop2.png|center|Fig.2 The DCC digital/analog tape head, showing the reversible disposition of digital heads 0–8 and analog heads A1 and A2.]] The tiny head gaps are formed by a lithographic thin-film process similar to that used to create microscopic layered circuits and conductive paths in silicon IC chips. Philips took advantage of this to devise a clever trick. First, the nine digital recording gaps are formed in a row, each 0.19mm high so that tracks of that width will be recorded on the tape. A thin insulating layer is added, and digital playback gaps are formed on top. Each is aligned with the center of the corresponding record gap but is only 0.07mm high. Result: since the short playback gaps read less than half of each recorded track, the tape can be misaligned relative to the head by as much as 0.12mm (plus or minus 0.06mm) and still play correctly. With this much tolerance for slop, DCC machines can use ordinary cassette mechanisms; costly machined parts and precise alignment won't be needed. (Incidentally, although the recording and playback gaps are separate, you can't use them to monitor the signal off the tape while making a recording. The gaps are so close together that magnetic coupling occurs between them.) A DCC machine communicates with the outside world through a standard Sony/Philips digital interface (S/PDIF), using the same 16-bit PCM codes as a CD player or R-DAT. Thus its digital input accepts 16-bit data from a CD player, and its digital output produces normal 16-bit data that can be fed to an outboard D/A converter or may be recorded on any conventional digital device (R-DAT, recordable CD, et al). In principle, you could even record live music on a DCC deck and use its digital output to master a CD. As in consumer R-DAT decks, digital dubbing is regulated by an SCMS circuit that allows any CD to be copied digitally onto tape but codes the copy so that it cannot be further copied. The analog input of a DCC deck is converted to PCM code by a normal 16-bit A/D converter, and the playback stage uses a conventional 16-bit D/A to generate its analog output. The choice of A/D and D/A circuits (conventional multibit, MASH, Bitstream, or whatever) will be up to each manufacturer of DCC machines. The heart of the DCC is a complicated block of circuitry called the PASC (Precision Adaptive Sub-band Coding), which a few years ago would have required a roomful of computer power and hours of processing time to do its job—which is to compress the incoming 16-bit digital data to an average of 4 bits per sample for recording and, during playback, to re-expand the 4-bit data to 16-bit output codes. As explained in the January 1991 issue, the encoding is done by a microprocessor programmed with information about the psychoacoustic limits of human hearing. The goal is to provide accurate coding of sounds we hear but not to waste bits coding information that we can't hear. The incoming 16-bit data stream is fed to a digital filter that divides the audio frequency range into 32 sub-bands, analyzes the signal content in each band, and uses only enough bits to encode the portions of the signal that are above the human threshold of hearing. The threshold varies with frequency (the Fletcher-Munson effect). A person with normal hearing can hear 2kHz at a very low 0dB sound-pressure level, but at 30Hz you can't hear anything softer than about 60dB spl anyway. More important, the threshold at each frequency varies from moment to moment according to the strength of sounds at neighboring frequencies ("masking"). Thus when an 80dB tone is present at 1kHz, your hearing threshold at 2kHz rises temporarily from 0 to about 50dB spl. Then, as long as the 1kHz tone is present, the system can safely discard any information below the 50dB level in the 2kHz sub-band—which may include the second harmonic of the 1kHz tone. If you wouldn't have heard it anyway, you won't notice its absence. Music, unlike noise, usually contains energy at only a few harmonically related frequencies. So at any given moment many of the 32 bands are likely to contain little or no energy. That frees many unused bits that can be assigned to provide more accurate coding in the bands that contain strong signals. This dynamic reallocation of bits between sub-bands plays a large role in the reduction of the overall bit rate. When fed a pure tone at a single frequency, nearly all of the available bits can be assigned to the sub-band containing this frequency, coding it with very low distortion. Conversely, when tested with pink noise, which contains equal energy in every band, all bands are active and only a few bits can be used for each; but since it is noise, high accuracy at each frequency isn't important. The most challenging test signal might be music of moderate complexity, exercising enough bands to use up the system's bit capacity while leaving enough "open space" in the sound that any faults could be heard. =Final development= According to Philips, the basic engineering design of the DCC system was completed in 1989. With a normal product the engineers would then measure a prototype to certify its performance with test signals, and would listen to it to make sure there was nothing obviously wrong. But since the DCC's encoding varies dynamically according to masking thresholds and other psychoacoustic criteria, its performance cannot be judged with conventional test signals. In the final analysis its sound quality can only be judged by ear. It sounded OK to the engineers, but masking thresholds may vary, and it is well known that some people hear sonic faults more acutely than others do. Moreover, golden-eared listeners aren't just born; they are trained (or train themselves), learning what to listen for and improving their skill with long practice. So, to evaluate whether the DCC could match the sound of CD, the designers turned to the trained listeners who are employed by the quality-control ~department at Philips Records (footnote 4). Listening to test signals and music, they did hear differences. So for the past two years Philips has been refining the PASC encoder, submitting it to listening panels, computer-analyzing the listening data with statistical programs to distinguish real differences from random chance and delusion, and fine-tuning the encoder again. Reportedly, after the latest round of refinements even the company's most golden-eared listeners can no longer distinguish the DCC from a CD source. Thus one of the largest electronics companies in the world found itself in the unusual position of fine-tuning the performance of an important new product in the same way the smallest cottage-industry audiophile designers do—by listening to it, with recorded music. And the company's engineers found themselves in the slightly humbling position of having to improve a product's design because non-engineers said it didn't sound quite right. The digital compression scheme has an interesting consequence. A DCC recorder accepts 16-bit PCM codes from a CD player, shrinks the bitstream to an average of four bits per sample for recording, then in playback regenerates 16-bit PCM output codes. The playback may sound the same as the original input signal, but the codes are not the same: the playback is a "cleaned up" version of the signal. The PASC processing puts the signal on a diet, stripping away the low-level musical harmonics that were below the dynamic masking threshold. Thus the playback signal, no matter how faithfully it may duplicate the original sound, is not a clone of the original code. You may recall that when the record industry launched its legal war to prevent the R-DAT from being sold in the US, one of its alleged concerns was that, if consumers acquired an unlimited ability to make "clone" copies of the digital code in a CD, record companies would effectively lose control of their expensively produced digital master recordings. Hypothetically, pirates with R-DATs could swamp the market with perfect clone duplicates of master tapes, depriving the record companies of their economic base. Of course, this idea contained more paranoia than reality; anyway, for what it's worth, the DCC doesn't make digital clone copies. That may help to explain why some record companies, at least, have expressed support for the DCC and will be mass-producing prerecorded DCC tapes for sale. Of course, the strongest support for DCC came from Philips's own PolyGram group of companies (Philips, DG, Archiv, Decca/London, L'Oiseau-Lyre, ECM, and Polydor), promptly followed by the EMI group (Capitol/Angel). BMG (RCA, Ariola, Arista) expressed interest in DCC but, like the rest of the record industry, wants Congress to impose a royalty tax on blank tape before the company will support any new recording medium. However, the momentum that seemed to be building in Congress to consider a royalty law was aborted by the Iraq war. Congress intends to devote itself to matters deemed more important than a squabble between branches of the entertainment industry. Philips has acquired two major partners in the DCC project. In the US, Tandy Corp. announced last fall its intent to be the first licensed manufacturer of DCC machines and tapes. Tandy is already North America's largest electronics manufacturer and, through its 7000 Radio Shack stores, our biggest retailer of consumer electronics. The company is expanding its role still further by launching new store chains (Video Concepts, The Edge in Electronics) and by being first with new technologies like notebook computers and the DCC. The decks and their digital circuits will be produced at Tandy's computer factory in Texas, while the tapes will come from Tandy's (formerly Memorex's) magnetic media plant in California, a major producer of computer disks as well as audio and video tapes. In Japan, Matsushita (parent of Technics and Panasonic), which has had a technology-sharing agreement with Philips for over a half-century, has also signed up for DCC. In fact, according to a Philips executive, Philips and Matsushita will be "co-licensors" of the DCC, in the same way that Sony and Philips are co-licensors of the CD. Companies that want to make DCC decks or tapes will have to get a license, pay royalties to Philips or Matsushita, and make sure that their products conform to the official design standard. In contrast, standards for R-DAT were developed by agreement among several manufacturers and are unenforceable. Example: since Congress failed to pass an SCMS/DRM law last year, the inclusion of SCMS in R-DAT decks is essentially voluntary, enforced only by Japan's Ministry of Trade and Industry. Companies in Korea and Taiwan are free to make R-DAT decks without SCMS if they wish. But in the case of DCC the SCMS circuit is mandatory; it is a condition of the license. All in all, the introduction of the DCC was the most impressive product launch since the CD, nine years earlier. If record companies get behind it—a crucial if—the DCC has a very good chance of knocking off both the R-DAT and the home-recordable CD as consumer products. Philips appears to have met its goal of combining CD-quality sound with the recordability, convenience, and compact size of the cassette. The first DCC machines probably will be AC-powered home decks and may be priced in the $600 range when they appear next year. By that time R-DAT decks may also be selling for $600, so we could see a brief format war between the two digital tape systems. But it won't last long; second- and third-generation DCC machines, notably play-only portables, car decks, and DCC boomboxes, could drop to the $200 level within a few years. Audiophiles and tape recording hobbyists may continue to prefer R-DAT, if only for its longer uninterrupted recording time, but DCC is likely to prove the true successor to the analog cassette. It's what my sister—and everyone else—will want. The largest remaining uncertainty is whether enough record companies will produce prerecorded DCC tapes to make it a mass-market success. At the moment the record companies that have committed to the DCC are all European. If the Recording Industry Association of America were to decide that the SCMS offers no protection and all digital recording formats must be fought until a royalty tax is passed, the US launch of DCC could be nearly as slow and painful as that of R-DAT. If DCC gets the support of major record companies, and cuts the ground out from under R-DAT, Sony still has an alternative up its corporate sleeve: the tiny Digital Memo Recorder (DMR), a simpler and cheaper mini-DAT that uses stamp-size cassettes. The truly interesting format war between digital tape systems may feature DCC vs DMR. Stay tuned.—Peter W. Mitchell Read more at https://www.stereophile.com/content/pasc-philips-dcc#xQLcVirM1owdzIfw.99 ecc724bac777ae79db88019bd8d216f4f01ac020 0 85 2342 1943 2019-02-13T17:16:44Z Pvdm 2 wikitext text/x-wiki =To check from which repo package came from= # rpm -qa --qf '%-20{NAME} %-20{VENDOR}\n' 'libav*5[678]' =To install only packages from one repo= #zypper in -r pvdm-kde43 amarok =Change the behaviour of download-install-download-install-download to download all-install all= modify /etc/zypp/zypp.conf and find and change: commit.downloadMode = DownloadInAdvance *[[How to locally cache zypper update files]] =upgrading your system using 'zypper dup'= *When you want to do an upgrade, "zypper dup" actually brings your system to the version of the available packages. This may mean downgrading and removing of installed packages. * The recommended way of doing this is to perform it against a specific repo: use zypper dup -from repo -r, --repo <alias|#|URI> Load only the specified repository. zypper dup -r 5 -r 6 -r 7 * If you intend to use "zypper dup" without any specific repostitory, you need to define repo priorities if you don't want to encounter surprises. * For the full story read [[http://duncan.mac-vicar.com/blog/archives/619 here]]. =if you want to find a certain file:= zypper in 'libqtiff.so()(64bit)' Reading installed packages... 'libqt4-x11' providing 'libqtiff.so()(64bit)' is already installed. Nothing to do. =if you want to install a certain version:= zypper in MozillaFirefox \>= 3 Other examples: zypper in yast* # install all yast modules zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server) zypper in vim -emacs # install vim and remove emacs in one go zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory zypper in -f subversion # force reinstallation of subversion =search packages= zypper search -s --match-exact virtualbox-ose Reading installed packages... S | Name | Type | Version | Arch | Repository --+----------------+---------+------------+--------+------------------------------------ v | virtualbox-ose | package | 1.6.2-2.1 | x86_64 | VirtualBox OSE i | virtualbox-ose | package | 1.5.6-33.1 | x86_64 | openSUSE-11.1-Oss v | virtualbox-ose | package | 1.5.6-20.5 | x86_64 | VirtualBox OSE ( v | virtualbox-ose | package | 1.6.2-2.1 | i586 | VirtualBox OSE v | virtualbox-ose | package | 1.5.6-33.1 | i586 | openSUSE-11.1-Oss v | virtualbox-ose | package | 1.5.6-20.3 | i586 | VirtualBox OSE =patterns= list patterns: zypper patterns =information on packages= zypper if amarok Information for package amarok: Repository: @System Name: amarok Version: 2.2.0-38.1 Arch: x86_64 Vendor: obs://build.opensuse.org/KDE Installed: Yes Status: up-to-date Installed Size: 24.2 MiB Summary: Media Player for KDE Description: Amarok is a media player for all kinds of media. This includes MP3, Ogg Vorbis, audio CDs, podcasts and streams. Play lists can be stored in .m3u or .pls files. Other examples: zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch zypper patch-info MozillaFirefox # the same as above zypper info -t pattern lamp_server # show info about 'lamp_server' pattern zypper info -t product openSUSE-FTP # show info about specified product =dependencies= what-provides or wp To list all providers of specified capability, do: <pre> zypper wp firefox Reading installed packages... S | Name | Type | Version | Arch | Repository --+----------------+---------+-------------+--------+------------------ i | MozillaFirefox | package | 3.0-0.1 | x86_64 | Updates for 11.1 v | MozillaFirefox | package | 2.9.95-25.1 | x86_64 | openSUSE-11.1-Oss v | MozillaFirefox | package | 3.0-0.1 | i586 | Updates for 11.1 v | MozillaFirefox | package | 2.9.95-25.1 | i586 | openSUSE-11.1-Oss </pre> Regarding optional dependencies, we do have them, and use them. They're enabled by default. To avoid the several hundred unexpected packages like in the example in the article you can use zypper with --no-recommends or turn them off in the zypper.conf config file. The zypper summary before an installation distinguishes between hard dependencies and recommends, so you can see what turning recommends off would have saved you even if you didn't. =package locks= To lock all packages starting with 'yast2', do: zypper al 'yast2*' Reading installed packages... Specified lock has been successfully added To list currently active locks: zypper ll # | Name | Type | Repository --+------------------+---------+----------- 1 | libpoppler3 | package | (any) 2 | libpoppler-glib3 | package | (any) 3 | yast* | package | (any) To remove a lock, do: zypper rl yast2-packager Other examples: zypper al zypper # lock package 'zypper' (exact match) zypper al -r repo-oss virtualbox* # restrict the lock to 'repo-oss' repository (allowing installation from others) zypper rl 3 # remove lock by number =rpm examples= # rpm -qi amarok Show details of package # rpm -qf /usr/sbin/sshd Shows where file came from # rpm -qR openssh-server Show dependencies - What do I need for this package to work? # rpm --whatrequires initscripts Find reverse dependencies - What will break if I remove this package # rpm -qip Show details of not yet installed package # rpm --verify openssh-server Find out if any files in the package have been modified since install. # rpm -qlv postfix list all files in a rpm 6dec974a7d3e1440b5a3ea61f8c56bf104dd282c 0 150 2344 2343 2019-03-09T09:38:43Z Pvdm 2 /* statusline */ wikitext text/x-wiki =vi editor tips= ==Keys== {| style="border-spacing:0;" | style="background-color:#99ccff;border:0.0007in solid #000000;padding:0.0382in;"| '''''Key''(s):''' | style="background-color:#99ccff;border:0.0007in solid #000000;padding:0.0382in;"| '''''Movement'':''' |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| 0 (zero) | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| 1^st column on the line |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| ^ | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| 1^st '''non-blanc '''char on line |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| $ | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Last char on line |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| g_ | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Last '''non-blanc''' char on line |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| w | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Next word |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| W | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Next word and '''skip''' interpunction |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| e | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| End of current word |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| E | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| End of current word '''incl''' .interpunction |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| b | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Begin of current word |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| B | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Begin of current word '''incl'''. interpuction |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| ge | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| End of previous word |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| gE | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| End of previous word and '''skip''' interpunction |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| O | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Insert new line and switch to insert mode |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| |- | style="background-color:#99ccff;border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| '''''Key''(s):''' | style="background-color:#99ccff;border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| '''''Action'':''' |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| x | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Delete char '''under''' cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| X | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Delete char '''before''' cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| r | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Replace char under cursor with next typed char |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| d | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Delete chars until position of next command |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| dd | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Delete line |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| y | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Copy text until position of next command |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| yy | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Copy line |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| p | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Paste text '''after '''cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| P | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Paste text '''before '''cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| |- | style="background-color:#99ccff;border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| '''''Key(s):''''' | style="background-color:#99ccff;border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| '''''Selection:''''' |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| V | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Start selecting block of text |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| x | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Cut block of text |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| c | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Copy block of text |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| iw | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Word |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| aw | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Word '''incl''' spaces |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| is | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Sentence |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| as | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Sentence '''incl''' spaces |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| ip | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Paragraph |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| ap | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Paragraph '''incl''' spaces and '''empty''' lines |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| i( | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block between brackets |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| a( | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block '''incl''' brackets |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <nowiki>i<</nowiki> | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <nowiki>Block between < ></nowiki> |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <nowiki>a<</nowiki> | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block '''incl'''<nowiki> < ></nowiki> |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| i{ | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block between { } |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| a{ | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block '''incl''' { } |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| i” | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block between “ “ |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| a” | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block '''incl '''“ “ |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| i` | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block between ` ` |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| a` | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Block '''incl '''` ` |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| |- | style="background-color:#99ccff;border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| '''''Search: ''''' | style="background-color:#99ccff;border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| '''''Action:''''' |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| /text | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Search for text starting at cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| n | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Find next |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| N | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Find previous |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| // | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Repeat last search |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <nowiki>*</nowiki> | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Search forward for word currently under cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <nowiki>#</nowiki> | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Search backwards for word currently under cursor |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| :set hlsearch | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Highlights all matches |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| :set nohlsearch | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Disable ^ |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| :nohl | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Don't show highlights from last search |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| :set incsearch | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Enables incremental search |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| :set noincsearch | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Disables ^ |- | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| | style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| |} u undo cut multiple lines: ###yy delete rest of line from cursor: SHIFT-d ==To open multiple files on a window== *Horizontal split vi -o file-one file-two *Vertical split vi -O file-one file-two *Switch between the panes you are using. CTRL + W + Left key to activate left windows CTRL + W + Right key to activate right windows CTRL + W + Up key> to activate to windows above current one CTRL + W + Down key> to activate to windows down current one *Split Open one file at a time vi file-one *To open the second file, go to the command mode (Esc) :new file-two OR :split file-two *to split vertically :vsplit *Typ 'CTRL-w w' to switch between the windows *Open new file: :e newfile ===Tabs=== To open Vi with multiple tabs open: vi -p /var/log/*.log *switch between tabs with ''gt'' *open new tab :tabnew or :tabe file to open new file in new tab ==Search and Replace== Go in command mode and type: Replace First occurence of string :%s/string-to-replace/replace-with-string/ Replace All occurence of string :%s/string-to-replace/replace-with-string/g Replace All occurence of string with confirmation :%s/string-to-replace/replace-with-string/gc ===avoid staircase effect when pasting=== If you're working in Vim and paste something into the terminal, sometimes you'll get a "staircase" effect where each line is progressively spaced farther outward, like so: <pre> line 1 line 2 line 3 line 4 </pre> Obviously, this isn't usually desirable. To correct this, you can enable paste to prevent the staircase effect. In command mode, type: :set paste This isn't on by default. When paste is enabled, it disables mapping and some other functions, so you probably want to know how to turn it off as well: :set nopaste ==Highlighting== syntax highlighting for programming languages :syntax on =Store settings= Put your most used commands, like '':syntax on'' in ~/.vimrc =statusline= set statusline=%F%m%r%h%w%=\ [%Y]\ [%{&ff}]\ [%04l,%04v]\ [%p%%]\ [%L] in /etc/vimrc d6c97ed8f335304dd39d5eb38623c74af29f1766 0 522 2349 2229 2019-04-12T07:30:36Z Pvdm 2 wikitext text/x-wiki @tecra:~> acestreamengine --client-console @tecra:~> acestream-launcher -p vlc acestream://67665adae9b7535a10f7b7a22d43f15683e78bde https://acestreamid.com/channel/sky-sports-f1 9f0fbb9a60f51aca2a4cb8a89597810d5384a6b9 0 561 2361 2360 2019-06-04T17:46:34Z Pvdm 2 wikitext text/x-wiki *[[enable 3d acceleration]] 84495556ea3fee9d44e994e0e78b2d8e7560b9ee 0 564 2365 2364 2019-06-11T14:20:45Z Pvdm 2 wikitext text/x-wiki =Can’t start X11 applications after “su” or “su -” to another user= To get access to the X client applications such as system-config-date, xclock, vncviewer we need to export the DISPLAY settings of a remote host to the local server. This is commonly done using below commands. # ssh root@remotehost remotehost# export DISPLAY=x.x.x.x:y.y Where x.x.x.x:y.y – is the display settings of the system from which you connected to the remote host. You can also use the -X option with ssh to directly export the DISPLAY on the remote host. # ssh -X root@remotehost But now if you try to switch to another user on the remote system and export the display again, you would get and error – “Error: Can’t open display:”. # ssh -X root@remotehost # su - [username] # export DISPLAY=x.x.x.x:y.y # xclock Error: Can't open display: x.x.x.x:y.y =X11 forwarding for sudo users= Just setting the DISPLAY is not enough. X authentication is based on cookies, so it’s necessary to set the cookie used by the user that initiated the connection. The following procedure allows a sudo user to use the ssh based X11 tunnel: 1. Connect the remote host using the -X option with ssh. # ssh -X root@remote-host 2. Now list the coockie set for the current user. # xauth list $DISPLAY node01.thegeekdiary.com/unix:10 MIT-MAGIC-COOKIE-1 dacbc5765ec54a1d7115a172147866aa # echo $DSIPLAY localhost:10.0 3. Switch to another user account using sudo. Add the cookie from the command output above to the sudo user. # sudo su - [user] # xauth add node01.thegeekdiary.com/unix:10 MIT-MAGIC-COOKIE-1 dacbc5765ec54a1d7115a172147866aa 4. Export the display from step 2 again for the sudo user. Try the command xclock to verify if the x client applications are working as expected. # export DISPLAY=localhost:10.0 # xclock 51d9e8e1f0de6dbdcdbf1ab1998ccf876239e477 0 560 2367 2348 2019-06-20T09:21:19Z Pvdm 2 wikitext text/x-wiki # zypper in python3-certbot-apache # certbot --authenticator standalone --installer apache -d www.reeltoreel.nl --pre-hook "systemctl stop apache" --post-hook "systemctl start apache" <pre> Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer apache Running pre-hook command: systemctl stop apache Obtaining a new certificate Performing the following challenges: http-01 challenge for www.reeltoreel.nl Waiting for verification... Cleaning up challenges Running post-hook command: systemctl start apache Deploying Certificate to VirtualHost /etc/apache2/vhosts.d/reeltoreel-le-ssl.conf Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Enhancement redirect was already set. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Congratulations! You have successfully enabled https://www.reeltoreel.nl You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=www.reeltoreel.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: Your key file has been saved at: Your cert will expire on 2019-06-20. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le b4788b644d1a2ea53033391a3e3690c3cff12b1a 0 14 2368 2179 2019-07-20T14:00:27Z Pvdm 2 wikitext text/x-wiki *[[ssh keygen]] *[[2do2018]] *[[VUmc]] *[[Create a bootable windows 10 USB stick from linux]] *[[Planten]] *[[Convert .flv to other movie format]] *[[Convert .img to .vdi for use with VirtualBox]] *[[Radiostation URLs]] *[[addresses]] *[[Watch]] *[[Timetable home-work]] *[[wijn]] *[[Software regelmatig te checken]] *[[bergschoenen checklist]] *[[printers2consider]] *[[teac mixers]] *[[DVB-C MythTV Ziggo]] *[[Online diagrameditors]] *[[Veluwe]] *[[touchpad]] *[[newcastle]] *[[gpsbabel]] *[[Oostenrijk 2012]] *[[Op te nemen films]] <pre> [:I:M:G:SPACE:W:I:D:T:H:=:6:0:0:]:SPACE:SPACE:[:/:I:M:G:]:LEFT:LEFT:LEFT:LEFT:LEFT:LEFT:LEFT:CTRL+V:RIGHT:RIGHT:RIGHT:RIGHT:RIGHT:RIGHT:RIGHT:ENTER 88aff75a61c38567994a4d10c3f9af202b5c75de 0 565 2369 2019-07-20T14:01:08Z Pvdm 2 Created page with " # ssh-keygen -t ecdsa -b 521" wikitext text/x-wiki # ssh-keygen -t ecdsa -b 521 05ba7886d0023b7fdd924de68d43420c309c2623 0 563 2370 2362 2019-07-31T10:38:21Z Pvdm 2 wikitext text/x-wiki Re: How to turn on OpenGL on RPi 3B (Solved) Quote Sun Oct 14, 2018 11:04 pm https://www.reddit.com/r/openSUSE/comme ... _question/ OP sdoconnell "3 months ago", 2018-07-xx. He found the solution in https://www.suse.com/documentation/suse ... rry-pi.pdf the SuSE documention for SLES-12 SP3 on Raspberry Pi (PDF). I did the following procedure with no problems on two different Raspberry Pi 3B's: 1. Since Eric Anholt's accelerated vc4 driver is "experimental", SuSE ships it with 3D acceleration suppressed. Edit /etc/X11/xorg.conf.d/20-kms.conf and comment out Option "AccelMethod" "none". 2. Install package Mesa-dri-vc4 which provides the direct rendering module for the X-Server. 3. In /boot/efi/extraconfig.txt you need dtoverlay=vc4-kms-v3d or dtoverlay=vc4-fkms-v3d ("fake" KMS). Other forum posts suggest that the latter one works better for streaming video, so I'm using that one. 4. The kernel command line needs a nonzero cma allocation. Based on another forum post I'm using cma=300M (unit of megabytes is required). Different people recommend different values. I suspect without proof that this is an upper bound; the driver is known to expand and contract video RAM dynamically. While other distros use /boot/cmdline, SuSE uses Grub (yay) which obeys /boot/grub2/grub.cfg which is overwritten on each update with material from /etc/default/grub. For this driver gpu_mem is irrelevant and can be left at the default (32 on SuSE, 16 on Gentoo, in megabytes). 5. Reboot, to get the changed dtoverlay=vc4-fkms-v3d and/or cma=300M. I installed glmark2 from the SuSE repo and it got an overall score of 74, which looks like the average frames per sec of the 33 sub-tests. Comparing the overall score on different graphics platforms: * 17 fps for a RPi 3B with software rendering. * 74 fps for a RPi 3B with the GPU enabled, 4.4x faster. * 1831 fps for an Intel Core i5-5200U @2.2GHz with Intel HD Graphics 5500. * And a real gaming GPU would be faster than that. So you won't be playing modern video games, but this is very promising for my goal of video playback. The next step is to purchase the codec licenses and install Kodi. Thank you to all who helped out on this issue and special credit to sdoconnell. --------- sdoconnell solved the problem! He has what he describes as a stuipdly simple solution, which he found in section 1.2.5 of the SLES documentation for Raspberry Pi. Jimc's paraphrase and extension of his solution: * Edit /etc/X11/xorg.conf.d/20-kms.conf and hide (comment out) 'Option "AccelMethod" "none"' to de-suppress direct rendering. SuSE turns it off by default because the vc4.ko driver by Eric Anholt is "experimental". An issue is described below, and as of 2018-09-xx to present (2018-12-xx), GPU acceleration with this problem really would not be acceptable in the SLES context. [Update: comments from a SuSE distro manager indicate that since Mesa-dri-vc4 is also not installed by default, they may or may not be going to get rid of 20-kms.conf.] * You also need to install package Mesa-dri-vc4 which provides the direct rendering module for the X-Server. It also is kept off the SLES installation and has to be installed explicitly by the user. * In extraconfig.txt you need dtoverlay=vc4-kms-v3d . Other forum posts suggest that dtoverlay=vc4-fkms-v3d ("fake" KMS) works better for streaming video and that's what jimc is using. * Comments on Gentoo say that the accelerated vc4 driver should not have a big gpu_mem allocation; they give gpu_mem=16 (no unit, megabytes is implicit). SuSE default is 32. This is in config.txt. * On SuSE, put local hacks in extraconfig.txt because config.txt gets altered in updates. It includes extraconfig.txt at the end. * The kernel command line needs cma=256M. The unit (megabytes) is required. This lets the GPU acquire memory dynamically, and jimc suspects without proof that this is an upper bound. Various amounts are seen in different forum posts. 256M is what Gentoo uses, and 300M is from a forum post that appears fairly authoritative to jimc. On SuSE the kernel command line is provided by Grub and the origin, editable by the sysadmin, is /etc/default/grub, which gets propagated to /boot/grub2/grub.cfg which you can tweak for experiments but which gets rebuilt in updates. Other distros get the kernel command line from /boot/cmdline.txt . * Look for CmaTotal and CmaFree at the end of /proc/meminfo. The default (on Gentoo without dtoverlay=vc4-kms-v3d) appears to be cma=8M. Limited experience suggests that dtoverlay=vc4-fkms-v3d sets a default of cma=256M, so you don't really need to set it explicitly on the kernel command line. In Gentoo. But in OpenSuSE if you leave it off you get zero CmaTotal and no GPU acceleration. 84f6ef55777df767706193a501ae51aa2456d0ea 0 473 2376 1819 2019-08-01T14:12:36Z Pvdm 2 wikitext text/x-wiki =check_mk= * download new version: https://checkmk.com/download.php?HTML=yes * # yum/zypper install <##> * # omd stop * # omd update <sitename> * # omd start =Introduction= This guide is intended to provide you with simple instructions on how to install Nagios from source (code) on openSUSE and have it monitoring your local machine inside of 20 minutes. No advanced installation options are discussed here - just the basics that will work for 95% of users who want to get started. These instructions were written based on an openSUSE 10.2 installation. =Required Packages= Make sure you've installed the following packages on your openSUSE installation before continuing. You can use yast to install packages under openSUSE. * apache2 * C/C++ development libraries ===Create Account Information=== Become the root user. su -l Create a new nagios user account and give it a password. /usr/sbin/useradd -m nagios passwd nagios Create a new nagios group. Add the nagios user to the group. /usr/sbin/groupadd nagios /usr/sbin/usermod -G nagios nagios Create a new nagcmd group for allowing external commands to be submitted through the web interface. Add both the nagios user and the apache user to the group. /usr/sbin/groupadd nagcmd /usr/sbin/usermod -a -G nagcmd nagios /usr/sbin/usermod -a -G nagcmd wwwrun ===Download Nagios and the Plugins=== Create a directory for storing the downloads. mkdir ~/downloads cd ~/downloads Download the source code tarballs of both Nagios and the Nagios plugins (visit http://www.nagios.org/download/ for links to the latest versions). These directions were tested with Nagios 3.1.1 and Nagios Plugins 1.4.11. wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.3.tar.gz wget http://prdownloads.sourceforge.net/sourceforge/nagiosplug/nagios-plugins-1.4.11.tar.gz ===Compile and Install Nagios=== Extract the Nagios source code tarball. cd ~/downloads tar xzf nagios-3.2.3.tar.gz cd nagios-3.2.3 Run the Nagios configure script, passing the name of the group you created earlier like so: ./configure --with-command-group=nagcmd Compile the Nagios source code. make all Install binaries, init script, sample config files and set permissions on the external command directory. make install make install-init make install-config make install-commandmode Don't start Nagios yet - there's still more that needs to be done... ===Customize Configuration=== Sample configuration files have now been installed in the /usr/local/nagios/etc directory. These sample files should work fine for getting started with Nagios. You'll need to make just one change before you proceed... Edit the /usr/local/nagios/etc/objects/contacts.cfg config file with your favorite editor and change the email address associated with the nagiosadmin contact definition to the address you'd like to use for receiving alerts. vi /usr/local/nagios/etc/objects/contacts.cfg ===Configure the Web Interface=== Install the Nagios web config file in the Apache conf.d directory. make install-webconf Create a nagiosadmin account for logging into the Nagios web interface. Remember the password you assign to this account - you'll need it later. htpasswd2 -c /usr/local/nagios/etc/htpasswd.users nagiosadmin Restart Apache to make the new settings take effect. service apache2 restart or systemctl restart apache2 Note Note: Consider implementing the ehanced CGI security measures described below to ensure that your web authentication credentials are not compromised. ===Compile and Install the Nagios Plugins=== Extract the Nagios plugins source code tarball. cd ~/downloads tar xzf nagios-plugins-1.4.11.tar.gz cd nagios-plugins-1.4.11 Compile and install the plugins. ./configure --with-nagios-user=nagios --with-nagios-group=nagios make make install ===Start Nagios=== Add Nagios to the list of system services and have it automatically start when the system boots. chkconfig --add nagios chkconfig nagios on Verify the sample Nagios configuration files. /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg If there are no errors, start Nagios. service nagios start or systemctl start nagios ===Login to the Web Interface=== You should now be able to access the Nagios web interface at the URL below. You'll be prompted for the username (nagiosadmin) and password you specified earlier. http://localhost/nagios/ Click on the "Service Detail" navbar link to see details of what's being monitored on your local machine. It will take a few minutes for Nagios to check all the services associated with your machine, as the checks are spread out over time. ===Other Modifications=== Make sure your machine's firewall rules are configured to allow access to the web server if you want to access the Nagios interface remotely. You can do this by: * Opening the control center * Select 'Open Administrator Settings' to open the YaST administrator control center * Select 'Firewall' from the 'Security and Users' category * Click the 'Allowed Services' option in the Firewall Configuration window * Add 'HTTP Server' to the allowed services list for the 'External Zone' * Click 'Next' and 'Accept' to activate the new firewall settings Configuring email notifications is outside the scope of this documentation. Refer to your system documentation, search the web, or look to the Nagios Support Portal or Nagios Community Wiki for specific instructions on configuring your openSUSE system to send email messages to external addresses. =Security= This is intended to be an introduction for implementation of stronger authentication and server security focused around the CGI web interface. '''Stronger Authentication using Digest Authentication.''' If you have followed the quickstart guides, chances are that you are using Apache's Basic Authentication. Basic Authentication will send your username and password in "clear text" with every http request. Consider using a more secure method of authentication such as Digest Authentication which creates a MD5 Hash of your username and password to send with each request. '''Forcing TLS/SSL for all Web Communication. ''' Apache provides TLS/SSL through the mod_ssl module. TLS/SSL provides a secure tunnel between the client and server that prevents eavesdropping and tampering using strong publickey/privatekey cryptography. '''Locking Down Apache Using Access Controls. ''' Consider locking down access to the Nagios box to your IP address, IP address range, or IP subnet. If you require access outside your network you could use VPN or SSH Tunnels. This is a easy and strong to limit access to HTTP/HTTPS on your system. ==Implementing Digest Authentication== The implementation of Digest Authentication is simple. You will have to create the new type of password file using the 'htdigest' tool, then modify the Apache configuration for nagios (typically /etc/httpd/conf.d/nagios.conf). Create a new passwords file using the 'htdigest' tool. The difference that you will notice if you are familiar with 'htpasswd' tools is the requirement to supply a 'realm' argument. Where 'realm' in this case refers to the value of the 'AuthName' directive in the Apache configuration. htdigest -c /usr/local/nagios/etc/.digest_pw "Nagios Access" nagiosadmin Next, edit the Apache configuration file for Nagios (typically /etc/httpd/conf.d/nagios.conf) using the following example. <pre> ## BEGIN APACHE CONFIG SNIPPET - NAGIOS.CONF ScriptAlias /nagios/cgi-bin "/usr/local/nagios/sbin" <Directory "/usr/local/nagios/sbin"> Options ExecCGI AllowOverride None Order allow,deny Allow from all AuthType Digest AuthName "Nagios Access" AuthDigestFile /usr/local/nagios/etc/.digest_pw Require valid-user </Directory> Alias /nagios "/usr/local/nagios/share" <Directory "/usr/local/nagios/share"> Options None AllowOverride None Order allow,deny Allow from all AuthType Digest AuthName "Nagios Access" AuthDigestFile /usr/local/nagios/etc/.digest_pw Require valid-user </Directory> ## END APACHE CONFIG SNIPPETS </pre> Then, restart the Apache service so the new settings can take effect. /etc/init.d/httpd restart ==Implementing Forced TLS/SSL== Make sure you've installed Apache and OpenSSL. By default you should have mod_ssl support if you are still having trouble you may find help reading Apache's TLS/SSL Encryption Documentation. Next, verify that TLS/SSL support is working by visiting your Nagios Web Interface using HTTPS (https://your.domain/nagios). If it is working you can continue on to the next steps that will force using HTTPS and block all HTTP requests for the Nagios Web Interface. If you are having trouble visit Apache's TLS/SSL Encryption Documentation and Google for troubleshooting your specific Apache installation. Next, edit the Apache configuration file for Nagios (typically /etc/httpd/conf.d/nagios.conf) by adding the 'SSLRequireSSL' directive to both the 'sbin' and 'share' directories. <pre> ## BEGIN APACHE CONFIG SNIPPET - NAGIOS.CONF ScriptAlias /nagios/cgi-bin "/usr/local/nagios/sbin" <Directory "/usr/local/nagios/sbin"> ... SSLRequireSSL ... </Directory> Alias /nagios "/usr/local/nagios/share" <Directory "/usr/local/nagios/share"> ... SSLRequireSSL ... </Directory> ## END APACHE CONFIG SNIPPETS </pre> Restart the Apache service so the new settings can take effect. /etc/init.d/httpd restart ==Implementing IP subnet lockdown== The following example will show how to lock down Nagios CGIs to a specific IP address, IP address range, or IP subnet using Apache's access controls. Edit the Apache configuration file for Nagios (typically /etc/httpd/conf.d/nagios.conf) by using the 'Allow', 'Deny', and 'Order' directives using the following as an example. <pre> ## BEGIN APACHE CONFIG SNIPPET - NAGIOS.CONF ScriptAlias /nagios/cgi-bin "/usr/local/nagios/sbin" <Directory "/usr/local/nagios/sbin"> ... AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.1 10.0.0.25 # Allow single IP addresses Allow from 10.0.0.0/255.255.255.0 # Allow network/netmask pair Allow from 10.0.0.0/24 # Allow network/nnn CIDR spec ... </Directory> Alias /nagios "/usr/local/nagios/share" <Directory "/usr/local/nagios/share"> ... AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.1 10.0.0.25 # Allow single IP addresses Allow from 10.0.0.0/255.255.255.0 # Allow network/netmask pair Allow from 10.0.0.0/24 # Allow network/nnn CIDR spec ... </Directory> ## END APACHE CONFIG SNIPPET </pre> Important Notes * Digest Authentication sends data in the clear but not your username and password. * Digest Authentication is not as universally supported as Basic Authentication. * TLS/SSL has potential for "man-in-the-middle attacks". MITM attacks are vulnerable if an attacker is able to insert itself between the server and client such as in a Phishing attack, ISP monitoring, or corporate LAN firewall certificate resigning. So read up on certificate verification! * Apache access controls only protect the HTTP/HTTPS protocols. Look into IPtables for strong system wide firewall control. * Most importantly, Security is a moving target so stay informed and do research! Perhaps by listening to a Podcast such as "Security Now!". 9b4f334c2a2ca3f3aef7bec020e4a99120328f9c 0 566 2382 2381 2019-08-10T19:48:28Z Pvdm 2 wikitext text/x-wiki =Specs= ==snaren | belts== 3 snaren: capstan, loader, tray. ===capstan=== * platte snaar maat 73mm x 3,7mm x 0,6mm. ===loader=== * ladesnaar groot straal| radius :27mm omtrek | circumference : 170 mm diameter | diameter : 54 mm platte lengte | flat lenght : 85 mm ===tray=== * ladesnaar klein straal| radius :14mm omtrek | circumference : 88 mm diameter | diameter : 28 mm platte lengte | flat lenght : 44 mm 44d0fbb6cc47c2415327fe819ae6a14ce602caed 0 567 2388 2387 2019-08-22T18:28:27Z Pvdm 2 wikitext text/x-wiki =belt= <pre> straal | radius : 36 mm omtrek | circumference : 228 mm diameter | diameter : 73 mm platte lengte | flat length : 114 mm </pre> 1ec3ee69b85da94a76452a4a480c8b480ce956cb 0 568 2405 2404 2019-09-06T07:08:03Z Pvdm 2 wikitext text/x-wiki This page is taken from the forum at tapeheads.net. It is reproduced here with the sole purpose to show the pictures in an easy way. The text is exactly the same. The original thread is located at: https://www.tapeheads.net/showthread.php?t=31379 ------------------------------------------------------------------------------------------------------------------------------------------------------------------- There are six basic categories of BASF true chrome tapes for compact cassettes: =chromdioxid SM 1971-80 are '''singe layer''' true chromes, with magnetial properties according to DIN reference tape C401R.= 1971-74:  http://www.vintagecassettes.com/basf/basf_files/image5036.jpg 1974-76:  http://www.vintagecassettes.com/basf/basf_files/image5098.jpg 1976-77:  http://www.vintagecassettes.com/basf/basf_files/image5175.jpg 1977-80:  http://www.vintagecassettes.com/basf/basf_files/image5187.jpg (77-79 without "hifi stereo cassette" badge, 79-80 with "hifi stereo cassette") =chromdioxid super SM 1977-80 are '''double layer''' true chromes with off-standard magnetical properties, still close to C401R, but higher sensitivity and a non-linear frequency range on DIN-aligned recorders:= 1977-80:  http://www.vintagecassettes.com/basf/basf_files/image5189.jpg (77-79 without "hifi stereo cassette" badge, 79-80 with "hifi stereo cassette") =chromdioxid II SM and Cr Extra II 1980-ca 1993 were '''single layer''' true chromes, with magnetial properties according to IEC II reference tape S4592A.= 1980-82:  http://www.vintagecassettes.com/basf/basf_files/image5245.jpg 1982-85:  http://www.vintagecassettes.com/basf/basf_files/image5304.jpg 1985-87:  http://www.vintagecassettes.com/basf/basf_files/image5327.jpg 1987-89:  http://www.vintagecassettes.com/basf/basf_files/image5347.jpg 1989-91: http://www.vintagecassettes.com/basf/basf_files/image5367.jpg 1991-93:  http://www.vintagecassettes.com/basf/basf_files/image5387.jpg 1993-95:  http://www.vintagecassettes.com/basf/basf_files/image5417.jpg =Cr Super II 1980-ca 1995, as well as Cr Maxima II 1982-ca 1994/95 are '''double layer''' true chromes with off-standard magnetical properties, still close to S4592A, but higher sensitivity and a non-linear frequency range on IEC-aligned recorders:= S 1980-81: http://www.vintagecassettes.com/basf/basf_files/image5246.jpg S 1981-82:  http://www.vintagecassettes.com/basf/basf_files/image5279.jpg S 1982-84: http://www.vintagecassettes.com/basf/basf_files/image5309.jpg S 1984-85: http://www.vintagecassettes.com/basf/basf_files/image5318.jpg S 1985-87:  http://www.vintagecassettes.com/basf/basf_files/image5329.jpg S 1987-89:  http://www.vintagecassettes.com/basf/basf_files/image5350.jpg S 1989-91:  http://www.vintagecassettes.com/basf/basf_files/image5370.jpg S 1991-93:  http://www.vintagecassettes.com/basf/basf_files/image5390.jpg S 1993-95:  http://www.vintagecassettes.com/basf/basf_files/image5420.jpg M 1982-85:  http://www.vintagecassettes.com/basf/basf_files/image5310.jpg M 1985-87: http://www.vintagecassettes.com/basf/basf_files/image5332.jpg M 1987-88:  http://www.vintagecassettes.com/basf/basf_files/image5352.jpg M 1988-91:  http://www.vintagecassettes.com/basf/basf_files/image5372.jpg M 1991-93:  http://www.vintagecassettes.com/basf/basf_files/image5392.jpg M 1993-95:  http://www.vintagecassettes.com/basf/basf_files/image5422.jpg The last examples of the 1993-95 line-up had already the next generation of tape described below. =CE II 1995 until the end: "'''single-layer''' chrome/ferric cobalt mix (85%/15%)" = (quoted from Wilhelm) with higher sensitivity compared to the older models, magnetical properties close to IEC II reference tape U564W http://www.vintagecassettes.com/basf/basf_files/image5437.jpg =CS II and CM II 1995 until the end (plus some 1994 Chrome Maxima II):= '''Double layer''' tape, the lower layer being the same mixture of ferric cobalt and chrome as in the CE II, and the upper layer pure chrome. Frequency response nearly as flat as a single layer tape, magnetical properties close to IEC II reference tape U564W http://www.vintagecassettes.com/basf/basf_files/image5440.jpg http://www.vintagecassettes.com/basf/basf_files/image5442.jpg With the last series of CS II during the Emtec era, I am not sure what tape they used. All four Maxima Design Editions had the contemporary Chrome Maxima tape. All budget chrome cassettes with different names, such as Chrome Standard II, ReCorD II, Sound (Level) II, the 353 Cr II Live as well as the Disney series and other printed shell promotional cassettes had one of the '''single layer''' chrome tapes, either the old Chrome Extra II or the new CE II formulation. =The Chrome II Super _Quality_ was specially made for Lidl discounter stores= Despite having the "Super" shell, I am not sure whether they had single layer CE II or double layer CS II tape inside: 1995-97:  http://www.vintagecassettes.com/basf/basf_files/image5484.jpg 1997-2002:  http://www.shizaudio.ru/audio/data/media/109/BASF-EMTEC_Chrome_Super_Quality_II_C90.jpg d4fe5469be147a7f1b5c5079da33def1268204a6 0 533 2406 2133 2019-09-07T17:48:42Z Pvdm 2 wikitext text/x-wiki <pre> Type IV - metal pigment (MP) [or metal evaporated (ME) tape whose extremely thin coating rendered it poor for analogue audio recording]. TDK made the official IEC reference tape. The pigment is such a small crystal that it can oxidize extremely quickly, enough to cause spontaneous combustion or explosions at any point in the milling/coating operation unless extreme precautions are taken, such as submersion in alcohol and a nitrogen-based environment. The particles were passivated with molecules of oxygen around the metal crystal to stabilize them because early metal tapes oxidized and lost magnetic properties. There were other experiments to modify the crystals with other metallic alloys either to enhance magnetic properties or to stabilize the crystals. Metal tapes are relatively environmentally stable with the lowest amount of print-through. They generally have the highest MOL and SOL values, but also the highest noise, so in practice they exceed Type II tapes only in low print and better high frequency dynamic range. Headwear is no different from that of any other magnetic pigment. Type III -ferric-chrome tapes. Sony made the IEC reference tape. Thicker coatings increased MOL, and the "underbiased" thin layer of chromium dioxide brought low noise. However, the disparity in bias points between the two layers meant a sagging mid-frequency sensitivity that had to be compensated by boosting record EQ to such a degree that SOL values were very poor. (This was common to double-coated tapes but far less pronounced when the optimum bias points were closer, as in BASF Superchrome tapes and TDK SA-X.) Type III tapes were never very popular and disappeared with the arrive of Type IV formulations. Headwear was the same as that for pure chrome tapes: lowest of all tapes for soft heads; higher initial wear on hard heads until the granular ferrite surface was polished, then very low with little to no gap erosion over the life of the head (except for some Sendust heads were chemical, not mechanical, erosion was observed similar to that induced by some ferric-cobalt formulations.) Type II - chromium dioxide or ferric-cobalt pigment. BASF made all Type II reference tapes, despite what TDK claimed in its misleading advertising. These tapes used either DuPont's invention of chromium dioxide (manufactured only by DuPont of BASF because of the enormous expense in heat/pressure reactors required to form the particle) or ferric oxides enhanced by the addition of magnetic cobalt to the crystal structure. Chrome was the first Type II tape, but Sony's exclusive distribution deal with DuPont forced other Japanese tape manufacturers to find an alternative in ferric-cobalt (an Agfa-Gevaert invention that they were never able to stabilize properly until the Japanese figured how to do it.) Chrome had the lowest noise because of its perfect particle size and near perfect uniformity that allowed easy distribution in dispersions and excellent alignment under orientation magnets in coaters, but the first chromes also broke in milling and were susceptible to high print-through. Ferric-cobalts allowed higher packing densities that increased tape sensitivity at the lower frequencies--a compatibility point that the Japanese used as a "quality" issue against chrome tapes--and allowed higher MOL values. The tapes, however, suffered from higher noise levels, which actually increased over time as delta noise, and from magnetostrictive effects that reduced high frequency signals under pressure from the capstan/pinch roller combination. Chrome suffered from neither and actually had its noise level decrease over time--along with output--so the dynamic range stayed the same while Dolby noise reduction tracking was compromised a bit--with a slight loss in accuracy but a pleasant increase in treble response. BASF redesigned its milling operations to reduce print-through to levels equal to or better than ferric-cobalt tapes and improved MOL and SOL values with new particles and finally, the introduction of ferric-cobalt oxides with chrome for the "Chrome Extra" formulations. The same improvements were made to the double-coated Superchromes and Chrome Maxima tapes. TDK, frustrated by chrome's claims to be the "world's quietest tape," introduced double-coated SA-X with a very fine ferric-cobalt particle coated on top of the standard SA formulation. This lowered noise levels about a decibel or so below that of pure chrome tapes (before delta noise set it) but brought the curse of increased print-through due to the presence of para-magnetic particles among the finely milled top layer particles. All producers of ferric-cobalt tapes made improvements to formulations that slowly increased output levels with few compromises to dynamic range. BASF itself introduced a ferric-cobalt tape in a heat-resistant housing for car stereo use because chrome's low Curie point meant that signals could be lost if the tape were subjected to high levels of heat. (This worked to chrome's advantage when used in highs-speed TMD thermal magnetic video duplication.) Barium ferrite was an alternative pigment considered for audio but seldom used except for some video applications. Despite the nasty headwear scare used to dissuade people from using chrome tape, there is little difference in the amount of wear induced by any Type II tape that is properly calendered and finished. (All lubricant, emulsifiers, static reducers, and fungicides are in the magnetic dispersion. They are not added later in the manufacturing process.) There were some Type II metal tapes in the market to offer metal recording for older tape decks without Type IV settings, but the lower MOL and SOL values along with the very high noise levels and inability to be erased eventually killed these interlopers. The best ferric-cobalts and chromes easily outperformed these metal pigment products. Chrome tapes had their greatest day in audio duplication because BASF encouraged duplicators to use a playback EQ of 120 microseconds and back off the record pre-emphasis to improve SOL values by almost 5 decibels. (The 70-microsecond EQ setting came about when no one expected Dolby NR to become standard. Had the engineers known Dolby would be so successful, they would have left playback EQ the same for Type II tapes as for Type I. Chrome/Dolby NR/70 microseconds were all introduced at the same time to reduce tape hiss--but any two of the three options would have been sufficient. All 3 at the same time was overkill.) Type I - ferric oxide, cobalt-modified ferric oxide. BASF made the official reference tape. These are the first and most common tapes. The range of quality levels is greatest in this class because the oxides can vary so much and because reject computer tape designed for digital signals, not audio, sometimes made its way into cheaper brands. Some of the best Type I tapes could offer low frequency signal-to-noise ratios that matched or slightly exceeded Type II and IV tapes, but their high frequency performance was never as good because of the lower coercivity of the oxides. These tapes, with their less sophisticated particles, tend to be the most environmentally stable over time as long as the binder formulations are stable. (Polyurethane binder breakdown is a plague among ferric reel-to-reel formulations from Ampex and Agfa; acid ooze is more common in cassette binder failures.) Headwear varies among tapes only because of different levels of quality in finishing the tapes: the better quality of tapes have no problem. Some ferric-cobalt Type I tapes have shown some chemical erosion on some Sendust heads, but one could argue whether it is the fault of the tape or the head design. In general, headwear is not a problem. (As a topic, headwear is a fascinating topic, rife with misinformation and rumors.) --------------------- DIN Type II Reference Tape C 401 R BASF 100% pure chrome IEC Type II Reference Tape S 4592A BASF 100% pure chrome IEC Type II Reference Tape U 564 W (replaced S 4592 A in October, 1987, in the IEC meeting in Prague) Magnetic Media Information Services, Volume XIII, No. 5 (August 20, 1993) discusses the technical work of Dr. Manfred Ohlinger, BASF's chief of pigment development. Dr. Ohlinger discussed work on CK60/XH, a chrome pigment with a coercivity beyond 1000 oersteds. He had already produce CK/75/230X with a value of 900 oe. and CK57/200X with a value of 670 oe. BASF was in full development of advanced pure chrome pigments for new 3480 cartridges and other media. BASF had been producing pure chromium dioxide pigments in a huge reactor in Ludwigshaven, Germany, since the late 1960s. In 1995 the oxide lineup included: CK 40-14 for audio tape CN 43-11 for high performance, single-coat audio tapes CK 37-11 for the lower coating of high performance chrome audio tapes. This pigment was designed for non-cross-linked binders. CK 48-21 was for the upper layer in cross-linked dispersions. These oxides were used in Chrome Super and Chrome Maxima tapes. The tapes were identical and differed only in the housing and the tighter specs for Chrome Maxima. Most Chrome Super performed exactly the same as Chrome Maxima. CK 50-21 was pure chrome used in VHS, S-VHS, TMD, and DCC formulations. (BASF made the only DCC tape. It was the tape in TDK and every other DCC cassette made.) There were CC variations of these pigments. They differed in that oxygen molecules were attached to the crystal surface to prevent degradation to hexavalent chrome in the presence of water. BASF used 100% pure chrome formulations for its EE reel-to-reel tape and for Loop Bin Master 920 and 921 used in the duplication industry before digital bins arrived. The only "hybrid" chrome/cobalt audio formulations appeared with the introduction in 1993/94 of "Chrome Plus" duplicator tape that had a small percentage of cobalt-ferric pigment added to raise AT315/MOL315. Its AT315 was 2-3 dB better than competing chrome tapes. Chrome Plus was also used in Chrome Extra audio cassettes from that point forward. In 1992 world-wide production of magnetic powder by weight was 11% for chromium dioxide, 55% for co-fe, 32% for standard ferric, and 2% for metal powder. This total includes all applications: audio, video, computer data. In 1994 BASF used a high-performance plastic that could withstand 95 degrees C. (203 degrees F.) without deformation. This plastic was used in the sonically welded Reference Maxima series. The tape was BASF ferric-cobalt because the heat resistance of the plastic would be wasted on a tape that had a much lower Curie point. (It was chrome's low Curie point that made it the only choice for thermal duplication--TMD--that was used for high-speed video tape duplication.) BASF kept Chrome Maxima and Chrome Super in the cassette lineup as 100% pure chromium dioxide tapes and the 85/15 Chrome Extra as its first and only hybrid chrome audio tape. As for "audiophile" opinions, I remember reading a discussion in The Absolute Sound condemning the process. It was obvious that the writer, an editor at the magazine, had little idea of magnetic recording. If you want an audiophile journalist's perspective on high-speed duplication, you would have to turn to John Borwick or Angus MacKenzie's work in British publications. </pre> =DCC tape= Quote: The tape formulations supplied by manufactures was actually from video tape stock rather than cassette stock, i.e. mostly chromium tapes but cobalt doped ferric formulations were also available at the least in the early days of DCC, for archival purposes the ferric formulations have a longer lifetimes despite the lower price, this use of video tape stock explains why metal tape playback is not officially supported in the DCC standard. A few chromium audio cassette formulations are very similar to video tape formulations so that it's theoretically possible to force some audio cassettes to work in a DCC recorder by modifying the enclosure and tape pad (if you need to seriously over-bias a chrome tape to make it sound right on an analogue recorder, chances are that it's video stock), but no audio cassette ferric formulations are similar to the video type ferric formulations that DCC expects. It's hard to make sense out of what the author is writing, partly because of poor grammar and punctuation, partly because of misinformation. DCC was NOT video tape "stock." It was audio base film coated with CK 50-21 pure chrome pigment, which was also used for VHS, S-VHS, and TMD video formulations in different dispersions and different processing. TDK, Panasonic, and other Japanese tape manufacturers didn't bother with producing ferric-cobalt DCC tape. They bought pancakes from BASF because they wanted a hand in the DCC jar just in case consumer demand picked up, but they didn't want to invest too much in risky development. (BASF initially did the same with DAT. We sourced the first BASF DAT tape. Tape manufacturers were being cautious at the time because there were too many formats to develop all of them and too many losses from the VHS consumer market.) The sentence fragment starting with "for archival purposes...." makes no sense to me. The same is true regarding metal tape playback. The author is probably British judging from the language used, so I don't know where he or she got the information. b6bb0ce94e3a4c037ed978f5742ed9e6a3990157 0 570 2414 2020-01-31T14:38:03Z Pvdm 2 Created page with "It seems to me that there is a lot of misunderstanding regarding what bit depth is and how it works in digital audio. This misunderstanding exists not only in the consumer and..." wikitext text/x-wiki It seems to me that there is a lot of misunderstanding regarding what bit depth is and how it works in digital audio. This misunderstanding exists not only in the consumer and audiophile worlds but also in some education establishments and even some professionals. This misunderstanding comes from supposition of how digital audio works rather than how it actually works. It's easy to see in a photograph the difference between a low bit depth image and one with a higher bit depth, so it's logical to suppose that higher bit depths in audio also means better quality. This supposition is further enforced by the fact that the term 'resolution' is often applied to bit depth and obviously more resolution means higher quality. So 24bit is Hi-Rez audio and 24bit contains more data, therefore higher resolution and better quality. All completely logical supposition but I'm afraid this supposition is not entirely in line with the actual facts of how digital audio works. I'll try to explain: When recording, an Analogue to Digital Converter (ADC) reads the incoming analogue waveform and measures it so many times a second (1*). In the case of CD there are 44,100 measurements made per second (the sampling frequency). These measurements are stored in the digital domain in the form of computer bits. The more bits we use, the more accurately we can measure the analogue waveform. This is because each bit can only store two values (0 or 1), to get more values we do the same with bits as we do in normal counting. IE. Once we get to 9, we have to add another column (the tens column) and we can keep adding columns add infinitum for 100s, 1000s, 10000s, etc. The exact same is true for bits but because we only have two values per bit (rather than 10) we need more columns, each column (or additional bit) doubles the number of vaules we have available. IE. 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024 .... If these numbers appear a little familiar it is because all computer technology is based on bits so these numbers crop up all over the place. In the case of 16bit we have roughly 65,000 different values available. The problem is that an analogue waveform is constantly varying. No matter how many times a second we measure the waveform or how many bits we use to store the measurement, there are always going to be errors. These errors in quantifying the value of a constantly changing waveform are called quantisation errors. Quantisation errors are bad, they cause distortion in the waveform when we convert back to analogue and listen to it. So far so good, what I've said until now would agree with the supposition of how digital audio works. I seem to have agreed that more bits = higher resolution. True, however, where the facts start to diverge from the supposition is in understanding the result of this higher resolution. Going back to what I said above, each time we increase the bit depth by one bit, we double the number of values we have available (EG. 4bit = 16 values, 5bit = 32 values). If we double the number of values, we halve the amount of quantisation errors. Still with me? Because now we come to the whole nub of the matter. There is in fact a perfect solution to quantisation errors which completely (100%) eliminates quantisation distortion, the process is called 'Dither' and is built into every ADC on the market. Dither: Essentially during the conversion process a very small amount of white noise is added to the signal, this has the effect of completely randomising the quantisation errors. Randomisation in digital audio, once converted back to analogue is heard as pure white (un-correlated) noise. The result is that we have an absolutely perfect measurement of the waveform (2*) plus some noise. In other words, by dithering, all the measurement errors have been converted to noise. (3*). Hopefully you're still with me, because we can now go on to precisely what happens with bit depth. Going back to the above, when we add a 'bit' of data we double the number of values available and therefore halve the number of quantisation errors. If we halve the number of quantisation errors, the result (after dithering) is a perfect waveform with halve the amount of noise. To phrase this using audio terminology, each extra bit of data moves the noise floor down by 6dB (half). We can turn this around and say that each bit of data provides 6dB of dynamic range (*4). Therefore 16bit x 6db = 96dB. This 96dB figure defines the dynamic range of CD. (24bit x 6dB = 144dB). So, 24bit does add more 'resolution' compared to 16bit but this added resolution doesn't mean higher quality, it just means we can encode a larger dynamic range. This is the misunderstanding made by many. There are no extra magical properties, nothing which the science does not understand or cannot measure. The only difference between 16bit and 24bit is 48dB of dynamic range (8bits x 6dB = 48dB) and nothing else. This is not a question for interpretation or opinion, it is the provable, undisputed logical mathematics which underpins the very existence of digital audio. So, can you actually hear any benefits of the larger (48dB) dynamic range offered by 24bit? Unfortunately, no you can't. The entire dynamic range of some types of music is sometimes less than 12dB. The recordings with the largest dynamic range tend to be symphony orchestra recordings but even these virtually never have a dynamic range greater than about 60dB. All of these are well inside the 96dB range of the humble CD. What is more, modern dithering techniques (see 3 below), perceptually enhance the dynamic range of CD by moving the quantisation noise out of the frequency band where our hearing is most sensitive. This gives a percievable dynamic range for CD up to 120dB (150dB in certain frequency bands). You have to realise that when playing back a CD, the amplifier is usually set so that the quietest sounds on the CD can just be heard above the noise floor of the listening environment (sitting room or cans). So if the average noise floor for a sitting room is say 50dB (or 30dB for cans) then the dynamic range of the CD starts at this point and is capable of 96dB (at least) above the room noise floor. If the full dynamic range of a CD was actually used (on top of the noise floor), the home listener (if they had the equipment) would almost certainly cause themselves severe pain and permanent hearing damage. If this is the case with CD, what about 24bit Hi-Rez. If we were to use the full dynamic range of 24bit and a listener had the equipment to reproduce it all, there is a fair chance, depending on age and general health, that the listener would die instantly. The most fit would probably just go into coma for a few weeks and wake up totally deaf. I'm not joking or exaggerating here, think about it, 144dB + say 50dB for the room's noise floor. But 180dB is the figure often quoted for sound pressure levels powerful enough to kill and some people have been killed by 160dB. However, this is unlikely to happen in the real world as no DACs on the market can output the 144dB dynamic range of 24bit (so they are not true 24bit converters), almost no one has a speaker system capable of 144dB dynamic range and as said before, around 60dB is the most dynamic range you will find on a commercial recording. So, if you accept the facts, why does 24bit audio even exist, what's the point of it? There are some useful application for 24bit when recording and mixing music. In fact, when mixing it's pretty much the norm now to use 48bit resolution. The reason it's useful is due to summing artefacts, multiple processing in series and mainly headroom. In other words, 24bit is very useful when recording and mixing but pointless for playback. Remember, even a recording with 60dB dynamic range is only using 10bits of data, the other 6bits on a CD are just noise. So, the difference in the real world between 16bit and 24bit is an extra 8bits of noise. I know that some people are going to say this is all rubbish, and that “I can easily hear the difference between a 16bit commercial recording and a 24bit Hi-Rez version”. Unfortunately, you can't, it's not that you don't have the equipment or the ears, it is not humanly possible in theory or in practice under any conditions!! Not unless you can tell the difference between white noise and white noise that is well below the noise floor of your listening environment!! If you play a 24bit recording and then the same recording in 16bit and notice a difference, it is either because something has been 'done' to the 16bit recording, some inappropriate processing used or you are hearing a difference because you expect a difference. G 1 = Actually these days the process of AD conversion is a little more complex, using oversampling (very high sampling frequencies) and only a handful of bits. Later in the conversion process this initial sampling is 'decimated' back to the required bit depth and sample rate. 2 = The concept of the perfect measurement or of recreating a waveform perfectly may seem like marketing hype. However, in this case it is not. It is in fact the fundamental tenet of the Nyquist-Shannon Sampling Theorem on which the very existence and invention of digital audio is based. From WIKI: “In essence the theorem shows that an analog signal that has been sampled can be perfectly reconstructed from the samples”. I know there will be some who will disagree with this idea, unfortunately, disagreement is NOT an option. This theorem hasn't been invented to explain how digital audio works, it's the other way around. Digital Audio was invented from the theorem, if you don't believe the theorem then you can't believe in digital audio either!! 3 = In actual fact these days there are a number of different types of dither used during the creation of a music product. Most are still based on the original TPDFs (triangular probability density function) but some are a little more 'intelligent' and re-distribute the resulting noise to less noticeable areas of the hearing spectrum. This is called noise-shaped dither. 4 = Dynamic range, is the range of volume between the noise floor and the maximum volume. Source: head-fi.org Comments: #) The Nyquist theorem does not include amplitude quantization meaning infinite resolution, so it doesn't discuss quantization effects at all. #) There is no audio system in the world giving more than 20 clear bits of signal due to resistance and semiconductor noise chracteristics. #) You cannot "recreate" a single thing by dithering, just make it sounding more natural to the ears, especially when using noise shaping filters for the dither signal. #) It's not true ADC's do any dithering. Some of them do some lowpass filtering with noise shaping involved when delta-sigma type which happens not for the dithering purposes but for the signal itself. #) You cannot increase dynamic range by dithering. #) It's not dynamics killing people and affecting hearing but sound pressure with the given numbers of 140dB = pain, 160~180dB = death, respectively. You can listen to the signal with the 144dB dynamics not exceeding safe sound pressure limits, just set the volume appropriately. Sure, you won't hear the bottom of your dynamic range then. Answers: # True. # True. Most people believe that their 24bit DAC is actually a 24bit DAC, just marketing I'm afraid. # True. Dithering is just a process which should be used whenever a quantisation or re-quantisation is performed, to convert quantisation errors into un-correlated noise. # This one is not true. All ADCs use dither. Some 24bit ADCs use self-dither, in other words because the digital noise floor is so low (-144dB) the noise generated by their own internal components is enough to dither, but one way or another, they all dither. Also, all ADCs use a low-pass brick wall filter (anti-alias filter). Noise-shaped dither is not and should never be used in an ADC or when mixing. As the recorded channels are mixed the re-distributed noise is summed and can cause problems. The only time noise-shaped dither should be applied is during the last quantisation process. This usually means when converting the 24bit master from the recording studio into 16bit for CD release. # Sort of true. In an absolute sense CD has 96dB dynamic range, however if we move the noise that is down at the -96dB level to areas of the hearing spectrum where we are less sensitive (for example below 60Hz or above 12kHz). This gives a perceived improvement of dynamic range for 16bit. Bob Katz, the leading expert, reckons that about 120dB is the perceived dynamic range achievable with today's dithering technology. # True. Though of course by turning down your amp and not hearing the quietest sounds, then you are not hearing all the detail or the whole dynamic range, so it rather defeats the whole purpose of more dynamic range (more bits) in the first place. f4b19c1a37e9d774a6c9c4c21d00a0d3869b5384 0 571 2416 2020-04-22T07:51:04Z Pvdm 2 Created page with "<pre> parted /dev/sda resizepart 2 100%  fdisk -l /dev/sda  partprobe /dev/sda  pvresize /dev/sda2  </pre>" wikitext text/x-wiki <pre> parted /dev/sda resizepart 2 100%  fdisk -l /dev/sda  partprobe /dev/sda  pvresize /dev/sda2  </pre> a54599c5f37e66080cdfe2126ade447de15281fb 0 572 2456 2455 2020-05-24T16:30:20Z Pvdm 2 /* Tip: recording from other sources */ wikitext text/x-wiki This is a full stereo set, containing a DCC and ACC cassette deck, tuner, cd player and amplifier. =belts and rollers= ==Analog Compact Cassette (ACC) Deck== ===Capstan belt=== The belt on the ACC deck is 103 mm flat length, so: <pre> straal | radius : 33 mm omtrek | circumference : 206 mm diameter | diameter : 66 mm platte lengte | flat length : 103 mm </pre> * Width: 4 mm. * Thick: 0,5 mm. ===square belt=== The square belt is 65 mm flat lenght, so: <pre> straal | radius : 21 mm omtrek | circumference : 130 mm diameter | diameter : 41 mm platte lengte | flat length : 65 mm </pre> * Width: 1 mm. ===Pinch roller=== ==Digital Compact Cassette (DCC) deck== The mechanism is the same as in the Philips DCC951 and DCC730. ???? <= need to check this, not really sure about that. ===Capstan belt=== * capstanbelt lenght folded flat approx. 110 mm, or maybe a little bit shorter. <pre> straal | radius : 35 mm omtrek | circumference : 220 mm diameter | diameter : 70 mm platte lengte | flat length : 110 mm </pre> * Width 3 mm. * Thick 0,5 mm. ===Pinch roller=== * pinch roller: 13 x 6 mm, axis: 2 mm. ==CD player== ===Tray loading belt=== <pre> straal | radius : 13 mm omtrek | circumference : 80 mm diameter | diameter : 25 mm platte lengte | flat length : 40 mm </pre> =Tip: recording from other sources= And here is a top tip: you can indeed record from ACC -> DCC, and also from tuner -> DCC or tuner -> ACC, but you should not use those small preset buttons for recording. You proceed as follows: *Suppose you want to record from ACC -> DCC. Insert the ACC and the empty DCC, rewind the DCC, press REC PAUSE on the DCC, RECORD will appear on the display, the player will start writing LEAD IN etc., please wait for it, then press PLAY on the analog deck and on PLAY of the DCC. A recording is made from the ACC to the DCC. *Same for recording from Tuner to ACC or DCC: press REC PAUSE, press TUNER, and press PLAY. This works for both the analog deck and the digital deck. Good luck with it! 26f5b801e1323a18cd3e375de4d62ca927c3fd6e 0 573 2458 2020-06-06T11:19:53Z Pvdm 2 Created page with "To resolve this issue you need to enable chrome://flags/#load-media-router-component-extension" wikitext text/x-wiki To resolve this issue you need to enable chrome://flags/#load-media-router-component-extension 36a5987019f17e0d062d1ada5cc65fa2ef4ac213 0 443 2466 2465 2020-06-07T16:57:41Z Pvdm 2 wikitext text/x-wiki ENGLISH BELOW =HERSTELLING VAN CONTACTEN - PROFESSIONELE REINIGING EN ONDERHOUD VAN CONTACTEN= De optimale herstelling van elektrische contacten in 3 stappen. * Snel * Betrouwbaar * Economisch ==STAP 1== '''KONTAKT 60''' Lost corrosielagen op en herstelt het metaalcontact. Ter voorkoming van het risico dat na een bepaalde tijd corrosie optreedt, is het aanbevolen stap 2 en 3 te volgen. ==STAP 2== '''KONTAKT WL''' Verwijdert opgeloste corrosieproducten, vet en vuil. ==STAP 3== '''KONTAKT 61''' Vormt een dunne beschermende film die corrosie en slijtage voorkomt. ---- =Verdere op- en aanmerkingen= Veel contactsprays laten een olie achtige film achter welke beschermt tegen vocht en corrosie. Echter trekt deze laag ook weer vuil en stof aan wat juist weer voor kraken en storen kan zorgen in audio. Ik adviseer sprays van Kontakt Chemie, en dan de Contact WL. Deze contactspray spoelt vuil weg en verdampt volledig, dus laat ook niets achter. Een idee is om deze spray royaal op en tussen je potmeters los te laten, zodat het er werkelijk uitloopt en draai gedurende deze behandeling de potmeters een paar keer heen en weer. Herhaal dit een paar keer zodat de residues van de oude contactspray goed worden weggespoeld. Ga er eventueel achter aan met perslucht om het geheel goed droog te blazen en fohn het verhaal eventueel warm. Perslucht bevat immers altijd vocht en dat wil je ook niet in je potmeters hebben. De volgorde is 60-WL-61 (inplaats van WL gebruikt men soms IPA, werkt ook goed). Alleen Kontakt 60 gebruiken is niet voldoende en zal de contacten uiteindelijk aantasten (is licht zuur) en problemen veroorzaken in HF-schakelingen (diëlectrisch en enigszins geleidend) '''En gebruik voor potmeters geen Kontakt 60, dat vreet de ingewanden op. Gebruik Contact Cleaner 390 of Kontakt Tuner spray. ''' Tuner 600 (kontakt chemie) spray is prima deze verdampt volledig en laat geen residu achter, maar smeert ook niet, en of dat in een potmeter of schakelaar echt goed is? Vandaar het rijtje 60-WL-61 of 60-IPA-61. 390 is op basis van een Philipsrecept en zou "alles in 1" moeten zijn, maar de details ken ik niet. Gezien de reputatie op gebied van research en doordachte spullen (dit bedoel ik niet cynisch) die Philips had, zou het toch goed spul moeten zijn. Reden dat 60 bij metalen contacten vaak nodig is, is dat dit oxidelaagjes het effectiefst oplost (juist omdat het licht zuur is, werkzame stof is oliezuur als ik goed geïnformeerd ben). Tuner 600 zal goed reinigen, maar wat het met oxides doet weet ik niet. Zelf gebruik ik altijd Tuner600 om faders/potmeters te reinigen, als ze maar licht vervuild zijn tenminste. Werkt prima. Voor zware vervuiling, lukt het met Tuner600 niet. Uit elkaar halen is nog altijd het best idd. =ENGLISH - Treatment of bad contacts - professional cleaning and maintenance of contacts= 3 steps: ==step 1== Kontakt 60. Dissolves corrosion layers and restores metal contact. To avoid the risk of corrosion occurring after a certain period of time, it is recommended to follow steps 2 and 3. ==step2== KONTAKT WL Removes dissolved corrosion products, grease and dirt. ==step3== Kontak 61 This forms a thin protective film that prevents corrosion and wear. =Further notes:= Many contact sprays leave an oily film that protects against moisture and corrosion. However, this layer also attracts dirt and dust, which in turn can cause cracking and disturbance in audio. I recommend sprays from Kontakt Chemie, and then the Contact WL. This contact spray washes away dirt and completely evaporates, so it also leaves nothing behind. An idea is to liberally release this spray on and between your potentiometers, so that it really runs out and during this treatment turn the potentiometers back and forth a few times. Repeat this a few times so that the residues of the old contact spray are rinsed well. If necessary, go after it with compressed air to blow it completely dry and blow-dry the story if necessary. After all, compressed air always contains moisture and you don't want that in your pot meters. The order is 60-WL-61 (instead of WL one sometimes uses IPA, works well too). Using only Contact 60 is not sufficient and will eventually attack the contacts (is slightly acidic) and cause problems in HF circuits (dielectric and slightly conductive) '' 'And don't use Kontakt 60 for potentiometers, that will eat the guts. Use Contact Cleaner 390 or Kontakt Tuner spray. '' ' Tuner 600 (contact chemistry) spray is fine, it completely evaporates and leaves no residue, but does not lubricate, and whether that is really good in a potentiometer or switch? Hence the list 60-WL-61 or 60-IPA-61. 390 is based on a Philips recipe and should be "all in 1", but I don't know the details. Given the reputation for research and thoughtful stuff (I don't mean this cynically) that Philips had, it should be good stuff. The reason that 60 is often required for metal contacts is that these dissolve oxide layers most effectively (precisely because it is slightly acidic, the active substance is oleic acid if I am well informed). Tuner 600 will clean well, but I don't know what it does with oxides. I always use Tuner600 to clean faders / potentiometers, as long as they are slightly dirty. Works fine. For heavy pollution, Tuner600 does not work. Disassembly is still best. 9275aba3720c3af72929049e3ef268d0c44fce1b 0 576 2471 2020-07-15T11:34:28Z Pvdm 2 Created page with "The PR 99 is basically the "hot rod" version of the B 77. It's basically the same machine built for semipro applications. XLR connectors and the 19" rack capability as a stand..." wikitext text/x-wiki The PR 99 is basically the "hot rod" version of the B 77. It's basically the same machine built for semipro applications. XLR connectors and the 19" rack capability as a standard offerings are the most significant differences. Of course, the addition of the auto-locator on the MK ii was a valuable asset for the pro user. It came in 61 versions and were sold for 13 years. A damper pin was added on the right side (the B 77 has only one) and the framed was modified to accommodate the protruding head block. It's widely known that the electronics were fully revised and improved with some features built specifically for pro applications. Marino and his staff were still developing the cassette deck project under constant cost pressure in order to start developing the new project "PR 99". This machine was never designed to be domestic or to be in a living room. It was exclusively called "Revox" and it was highly successful! The PR 99 is the affordable "Studer". It was the bridge between the domestic B 77 and the professional Studer machine. The sales of the PR 99 among the professional circles were really amazing! Three versions were made: MK i, MK ii and MK iii. The MK i and the MK ii, besides the auto locator, are almost the same machine. The MK iii looks different because the bottom panel is gray color and the buttons are plastic. They wanted to give this last version a more "pro console" look, hence the new buttons (they were cheaper, too!). That's all. There's not a significant difference between the ii and iii and built wise has the same frame and construction. People don't understand that many of the so called revisions are in fact looking for improvements and mainly for lowering the production cost as well. That's the case of the MK iii. The 99' came with a metal 19" rack capability, on a cart or in a flight case with speakers for live recording applications. This last version is rare and I have only seen one. It's not of my personal liking as it's bulky, heavy and I wouldn't listen to my recordings through those shitty speakers anyway. The only value I see is from the collector's point of view and nothing else. On the other hand, those with the butterfly heads are more valuable and scarce. From the sonic point of view, it's not better sounding than its 77' cousins and some people insists that the addition of the balanced transformers for the XLR connectors made it worst than better. I don't care as I find both very pleasant and neutral sounding. There's not a significant difference, if any, in sound. That's for sure. Most of the time it just need somebody, from somewhere to say something, and others start repeating the same **** over and over again until soon enough a urban myth is created! 90% of the time people keep saying the same gossip without even hear or confirm it by themselves. That's the usual case in Audio. The other is when Mr. John Doe look at the design and says: "Oh!, there're balanced transformers on the output,so it has to sound bad!", without hearing the machine first. By that time, a prejudice is created and in no time the rest of the world keeps repeating the same **** as well. Period. The latest B 77's were built in Regensdorf at a rate of 175 units daily when the production was in full blast and were branded as "Studer". Many features from the A 77 were still in function in the B 77 and PR 99 as well. The A 77 replaced the now legendary 36 series and came in response to the Japanese market penetration. The A 77 is cataloged as one of the most important reel to reel decks in audio history and no discussion about tape recording in the 70's could be complete without the venerable A 77. Guido Besimo was in charge of the project. Hans Foletti and Herbert Romagna were in charge of the mechanics, Ernst Mathys designed the function control board, the capstan motor was from the genius of Artur Stosberg and the group's leader himself, Besimo, designed the audio circuit. The thing is that this A 77 audio circuit became the ReVox trademark for years to come and it was later used, without significant revisions, on the B 77 and PR 99 ! That's what I call a genuine cornerstone! The real genius of Studer has been to implement professional quality products in domestic models. As a matter of fact: many A 77 and B 77 were constantly used in professional studios and radio stations. Here in Puerto Rico, Radio Oro, kept using their A 77's array for over 30 years when they were finally retired to receive the new digital era. This same story has been repeated over and over again around the globe. I'm sorry but I don't think any model from Japanese brands could ever make the same allegation. I'm not saying those are bad machines. No. That's not what I mean, but there's an imminent truth in all this and that's the fact that ReVox were ahead of its time by far, as the actual longevity and parts availability testifies. You can still order brand new parts for your Revoxes. They were on another league. Revox products were aimed at domestic markets, but most of their machines were used in professional applications. That's how good they are and how much appreciation and acceptance were given by the professionals around the world. Another subject to consider is that, if we take into consideration that perhaps just one model from any Japanese brands were sold in bigger numbers than all the B 77's combined, how many of those still survives today against the Swiss gem? The A-77 and A 700 are still getting refurbished to this date by audiophiles around the world, even after 40 years! Perhaps that's why Studer-Revox products are among the most restored audio components in this hobby and fetching the highest prices in the second hand market. As a matter of fact: many of these machines has been sold for more of what their original prices were 30 years ago! The last B 77 MK ii and PR 99 MK iii left the manufacturing plant in 1997. source: tapeheads.net ac5a82ba9635e14d22153d3fadda0602194faaf7 0 499 2473 2472 2020-07-15T11:38:28Z Pvdm 2 wikitext text/x-wiki =Sam:= When I worked at Teac the Technicians had a discussion early on about how the bias should be set and we discussed the two ways to do it. We found and we told later on that the service manual is written for Technicians and often times with the assembly line in mind. Overbias is a fast and sloppy way to do the job to turn out more units from the line. =exact calibration= It is not found to be the way for exacting calibration. That can only be by either spot frequencies or sweeps as is available on a device like the Audio Precision One plus analyzer. Here the 1KHz and 10KHz are compared and then once those are close to each other further modification allow the frequency response be contoured to go out to extended frequencies such as 31.5KHz at 15 IPS or in some deck 28KHz. Of course you can not hear that but it shows what a machine can do. I have had factory decks come in that would be 3 dB down at 9KHz. =factory set= Is this what you call Hi Fi? I don't When I got done with the machine it went out to 22KHz at 0 Vu at 7.5 IPS. In all my years of working on decks I have had no negative comments about my calibration process either at Teac or Sony or after. In fact people often tell me they sound better than they were new. I suspect that is correct as they were probably set wrong from the factory which is common. The manufacture only provides you with a deck that works- it does not say it is optimum adjusted. That is why there is such a long list of tape in the manuals as it is set up somewhere in the range of all those tapes- none are perfect. I have not used over bias since 1982. I can send sweep results to those who wish to see them by E mail bit in the past I have already posted some of those. I use plus or minus 2 dB not 3dB. Some machines come out to plus or minus 1dB if it were not for the head bump. 26a90ccdc553dfbfad9f1180877a3b08d86126e1 0 575 2475 2468 2020-08-20T19:06:05Z Pvdm 2 wikitext text/x-wiki =When hanging like a ........= $ rm .config/session/kwin........... =to get into bootmenu= Fn+F12 dd8f74c42fbea07b21d12aeef3a4d8b34d7f73ba 0 577 2499 2498 2020-08-21T14:35:21Z Pvdm 2 /* Tape Transport */ wikitext text/x-wiki =Tape Transport= </div> {| style="border-spacing:0;width:30cm;" |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Track Configuration''' | style="color:#696969;" | 1/4" (6.3 mm) Width Tape, 2-track 2-channel, NAB or DIN Stereo |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Nom. Tape Speed''' | style="color:#696969;" | 38.1 & 19.05 cm/s (15 & 7.5 ips) switchableChangeable to 19.05 & 9.5 cm/s (7.5 & 3.75 ips) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Speed Accuracy''' | style="color:#696969;" | Within ±0.2% |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Speed Deviation''' | style="color:#696969;" | Less than 0.2% |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Pitch Control''' | style="color:#696969;" | ±20% continuously variable control.Percentage or ips readout with 0.01% precision multiturn encoder servo system. |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Fast Wind Time''' | style="color:#696969;" | 60 Hz = 100 s, 50 Hz = 110 s (2,500 ft tape) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Reel Size''' | style="color:#696969;" | NAB 10.5", 7", 5", EIA (cine), DIN ReelTape Max. Length = 3,280 ft (tape thickness 50 μm) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Motor''' | style="color:#696969;" | Capstan = DC Brushless Motor, Quartz PLL Controlled Direct DriveReel = AC Induction Motor |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Head''' | style="color:#696969;" | Plug in head block with full access to independent head height, tilt and azimuth adjustment |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Start Time(Time to reach within twice specified wow & flutter.)''' | style="color:#696969;" | 38.1 cm/s = Less than 0.5 s19.05 cm/s = Less than 0.3 s9.5 cm/s = Less than 0.2 s |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Wow & Flutter(PEAK WTD, DIN45507, IEC Pub.386)''' | style="color:#696969;" | 38.1 cm/s = Less than ±0.06%19.05 cm/s = Less than ±0.08%9.5 cm/s = Less than ±0.12% |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Tape Timer''' | style="color:#696969;" | Seven segment LED readout from tachometer/logic measurement circuit; indicates tape time in Hours, Minutes and Seconds. |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''External Speed Control Range''' | style="color:#696969;" | -50%, +100% at all speeds (4.8 to 19.2 kHz) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''VEM Tape Speed''' | style="color:#696969;" | +100% with VEM optional accessory and continuous lower speed change accompanying tone change |- |} =Electronics (Measured with AMPEX #456 tape. 0 dBu = 0.775 V)= </div> {| style="border-spacing:0;width:30cm;" |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;width=10cm;" style="vertical-align: top;" | '''Line Input''' | style="color:#696969;" | 3-pin XL Type Connector (female)<br> Transformerless Active Balanced<br> Input Impedance: 10 kΩ<br> Ref. Input Level: +4 dBu (0 to +10 dBu), -16 dBu (-10 to -20 dBu)<br> Max. Input Level: +30 dBu<br> |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Mic Input''' | style="color:#696969;" | 3-pin XL Type Connector (female) Transformerless Active Balanced<br> Input Impedance: 10 kΩ (20 Hz to 20 kHz)<br> Min. Input Level: -70 dBu<br> Microphone Impedance: 150 to 10 kΩ<br> With Supply Channel (CH1/BOTH/CH2) Selection Switch |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Line Output''' | style="color:#696969;" | 3-pin XL Type Connector (female) Transformerless Active Balanced (bal/unbal. switchable)<br> Output Impedance: 5Ω<br> Ref. Output Level: +4 dBu (0 to +13 dBu), -16 dBu (-7 to -20 dBu)<br> Load Impedance: min. 200Ω<br> Max. Output Level: +26 dBu (bal. load), +21 dBu (unbal. load) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Bias and Erase Frequency''' | style="color:#696969;" | 150 kHz |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Magnetic Flux Level''' | style="color:#696969;" | MX-55N = 185/250/370 nWb/m (switchable)<br> MX-55D = 250/320/510 nWb/m (switchable) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Frequency Response(Rec/Rep. 0 dB = 250 nWb/m)''' | style="color:#696969;" | 38.1 cm/s = 30 Hz to 20 kHz ±2 dB (0 dB)<br> 19.05 cm/s = 20 Hz to 18 kHz ±2 dB (-10 dB)<br> 9.5 cm/s = 20 Hz to 10 kHz ±2dB (-20 dB) |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Frequency Response(Sel-Rep)''' | style="color:#696969;" | 38.1 cm/s = 30 Hz to 12 kHz ±3 dB<br> 19.05 cm/s = 20 Hz to 5 kHz ±3 dB<br> 9.5 cm/s = 20 Hz to 2.5 kHz ±3 dB |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Distortion (38.1 cm/s, 1 kHz, 250 nWb/m)''' | style="color:#696969;" | Less than 0.3% |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Crosstalk''' | style="color:#696969;" | MX-55N = min. 55 dB<br> MX-55D = min. 50 dB |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Depth of Erasure(38.1 cm/s, 1 kHz, 1040 nWb/m)''' | style="color:#696969;" | MX-55N = min. 75 dB<br> MX-55D = min. 70 dB |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Rec/Rep Signal-to-Noise Ratio(30 Hz to 18 kHz BPF, UNWTD)''' | style="color:#696969;" | MX-55N NAB 38.1 cm/s, 1040 nWb/m = 69 dB<br> MX-55N NAB 19.05 cm/s, 1040 nWb/m = 71 dB<br> MX-55N NAB 9.5 cm/s, 740 nWb/m = 64 dB<br> MX-55N IEC 38.1 cm/s, 1040 nWb/m = 71 dB<br> MX-55N IEC 19.05 cm/s, 1040 nWb/m = 68 dB<br> MX-55N IEC 9.5 cm/s, 740 nWb/m = 64 dB<br> MX-55D IEC 38.1 cm/s, 1040 nWb/m = 72 dB<br> MX-55D IEC 19.05 cm/s, 1040 nWb/m = 69 dB<br> MX-55D IEC 9.5 cm/s, 740 nWb/m = 65 dB |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Test Signal Oscillator Frequency''' | style="color:#696969;" | 100 Hz, 1 kHz, 10 kHz Sine Wave, switchable |- |} =Miscellaneous= </div> {| style="border-spacing:0;width:30cm;" |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;width=10cm;" style="vertical-align: top;" | '''Power Requirement''' | style="color:#696969;" | 100/110/117/200/220/240 VAC, ±10%, single phase 50/60 Hz |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Power Consumption''' | style="color:#696969;" | 150 VA |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Operating Environment''' | style="color:#696969;" | Temperature: 5 to 45°C, Relative Humidity: 20 to 80% |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Storage Environment''' | style="color:#696969;" | Temperature: -20 to 45°C, Relative Humidity: 10 to 80% |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Weight''' | style="color:#696969;" | 30 kg |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" | '''Dimensions (W x D x H)''' | style="color:#696969;" | 440 x 222 x 488 mm |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Standard Accessories''' | style="color:#696969;" | NAB Reel Adapter<br> 10.5" Empty Reel (MX-55N only)<br> DIN 12" Empty Reel (MX-55D only)<br> Power Cord<br> Fuse 1 A x 2<br> Fuse 2 A x 4<br> Fuse 5 A x 1<br> Fuse 5 A (slow blow) x 1<br> Lubrication Oil (PZ9E003)<br> Case Foot Operaiton Manual |- style="border-top:0.05pt solid #dcdcdc;border-bottom:0.05pt solid #dcdcdc;border-left:none;border-right:none;padding-top:0.159cm;padding-bottom:0.159cm;padding-left:0cm;padding-right:0cm;" | style="color:#696969;" style="vertical-align: top;" | '''Optional Accessories''' | style="color:#696969;" | CB-127-S Remote Controller<br> ZA-81G-S Stand (with Reel Spacer. Tilt Adjustable)<br> ZA-81B-T Stand (without Reel Spacer)<br> ZA-81D-S Reel Spacer (for ZA-81B-T)<br> ZA-5CG Rack Mount Bracket<br> SB-12S Scissors<br> ZA-5CU Fader Control Kit<br> PB-1AXAS VEM (Voice Edit Mode) <br> PCBZA-5CW Proximity Switch Kit<br> ZA-5CX Multi Purpose Phone Jack Kit<br> ZA-5CL Input Transformer<br> ZA-5CM Output Transformer<br> |- |} cae7ca5891d9d23926c73287f3c1b3b2b67567c6 0 578 2501 2020-08-23T07:47:46Z Pvdm 2 Created page with " # echo 0 | sudo tee /sys/bus/cpu/devices/cpu$COREID/online # Disable a CPU core to save battery and lower thermals. Works greats if your laptop is noisy and you're only doing..." wikitext text/x-wiki # echo 0 | sudo tee /sys/bus/cpu/devices/cpu$COREID/online # Disable a CPU core to save battery and lower thermals. Works greats if your laptop is noisy and you're only doing light work c6811d0b1b7a4f775bc02f9c0afc8112ffb3435f 0 579 2503 2020-08-26T14:39:34Z Pvdm 2 Created page with " # echo "0 0 0" > /sys/class/scsi_host/host5/scan 5 is changeable; it is the connection" wikitext text/x-wiki # echo "0 0 0" > /sys/class/scsi_host/host5/scan 5 is changeable; it is the connection 0419d45197f942e5e6e386fda0986238d8a27f01 6 580 2504 2020-08-26T21:32:52Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 569 2505 2410 2020-08-26T21:36:05Z Pvdm 2 wikitext text/x-wiki Athana International - PF212 Degausser - Model PF 212 <gallery> GENEVA-Audio-Video-Bulk-Tape-Eraser-Model-PF-212.jpg|Model PF 212 </gallery> Computer/Video/Audio Tape Eraser (220 VAC; 50 Hz) The hand-held model PF 212 tape eraser is perfect for the low-volume user. A few seconds is all it takes to completely erase a tape. This convenient, easy-to-use machine will completely erase previous recordings in just seconds. Used computer tapes and diskettes can perform like new when erased with a wave of the PF 212 professional, powerful tape eraser. At 220 VAC, this machine is powered for European and Asian markets. The duty cycle is one minute on and five minutes off. Features: <pre> 2300 gauss flux field erases tapes to like-new condition Thermal fuse prevents overheating; resets automatically Easy to activate on/off power switch Rugged, comfort-molded ABS Cycolac case UL/CSA approved 220 VAC; 50/60 Hz power required </pre> Applications: <pre> Police recordings Fire department recordings TV broadcast recordings Ambulance training recordings Hospital recordings Bank data processing records Financial and insurance recordings Software duplicators Military video recordings Legal confidential diskette recordings Floppy disk recordings Video recordings Audio recordings TV screens CRT terminal screens Music industry audio recordings Data processing obselete records Media Erased: Diskettes: 3 1/2" and 5 1/4" diskettes, floppy disks Audio tape cassettes 10 1/2" computer reels Reel tape: 1/4" and 1/2" audio reels IBM 3480 and 3490 cartridges TK50, TK70 and TK75 tape cartridges DC 300, 600, 1000 and 2000 cartridges VHS and S-VHS videotape cartridges U-Matic cartridges Betacam videotape cartridges Compact cassettes Purchase Price $169.00 Shipping $9.95 Gauss 2300 Dimensions Width 5.5 inches 140 mm Length 10.25 inches 260 mm Height 3.75 inches 95 mm Weight 3 lbs 1.4 kg bdc49683b0aa18bbcd451a824e6d5fff6dbfe9a6 0 581 2515 2514 2020-09-02T16:37:28Z Pvdm 2 wikitext text/x-wiki # su to etherpad user # go to dir: /opt/etherpad/etherpad-lite # # git pull origin # e98eec624c727113746a8cd0ac2fafb9be2c696a 6 583 2522 2020-09-09T16:55:02Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 584 2526 2020-09-09T16:58:42Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 585 2533 2020-09-09T17:08:14Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 586 2538 2020-09-09T17:13:23Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 582 2541 2540 2020-09-09T20:06:51Z Pvdm 2 /* STEREO-MONO COMPATIBILITY */ wikitext text/x-wiki =JOSEF DORNER = ==From 15 MilliMaxwell to 1,200 NanoWebers == Need an explanation? Here's a look at the evolution of fluxivity and level standards. An EYE-CATCHING HEADLINE to attract or confuse the reader? Well, certainly not the latter, because one is often confused enough when trying to understand the data printed on the specification sheets accompanying many tape recorders. We find distortion performance and signal-to-noise ratios referred to 185, 200, 250, or even 370nWb/m. In some cases, flux values as high as 1,000 and even 1,040 nWb/m are mentioned, while Europeans use such odd values as 320 and 514 nWb/m for reference fluxivity. Where do all these different values come from? Maybe some light can be shed on this matter by looking back into the history of magnetic recording. ==A STANDARD IS CREATED== Let's go back about 30 years, to a time when Geman technicians were already talking about a standard tape flux, well before their cohorts on the other side of the Atlantic were. Their definition read something like this: "...for the purpose of program exchange, a reference value for remanent tape magnetization has to be established. When using general purpose tapes, this level shall be approximately 6 dB below maximum output level. (In reality, the span was only 4 dB at that time- author). Fortissimo passages shall modulate the tape up to that reference level. This is of importance for the purpose of program exchange. Only in applications where program exchange is not a criterion, modulation up to 3 percent of third-harmonic distortion may be tolerated; this is in order to achieve a higher signal-to-noise ratio and better utilization of the tape. For class 38 (15 ips) the reference level is set to 200 milliMaxwell and for class 19 (7.5 ips) to 160 milliMaxwell." (Draft for DIN 45 513).[1] Remember this dates back to 1955! In America, all that was known at that time, as far as a recording standard was concerned, was the calibration tape made by a well-known manufacturer of magnetic tape recording equipment (Ampex) with a reference level recorded on it, which was named the "Operating Level." That Operating Level was used to calibrate the VU-meter to obtain a 0 VU deflection. By digging a little deeper, one was able to learn that this Operating Level corresponded to 1 percent of third-harmonic distortion on the then most widely used (general purpose) recording tape in the USA. ==MOL AND THE VU METER== At this point it may be of interest to note that this general purpose tape produced 3 percent of third-harmonic distortion when it was modulated to a point some 6 dB above Operating Level. Many a studio (particularly some European studios) - where the VU-meter started to make its appearance in the early '60s - may have been misled by this fact to think that a VU-meter has to be operated with a 6 dB lead. By 1966, however, the Deutsche Industrie Normen (DIN) had already recognized that this was not quite correct, because it is stated in the explanatory note accompanying DIN 45 406 that "....on average the lead required is about 8 dB (8 VU). Deviations from this average by ±5 dB, however, are not exceptional." If one compares this with the old RETMA TR 105 B standard (1951) for Audio Facilities for Broadcasting Systems, one can read the following in section V.2.a: "If a VU-meter is incorporated, it shall remain as normally connected, and its multiplier shall remain set for a signal which is 10 dB below standard output level" (Standard output level is +18 dBm). Can one not conclude from this that signal peaks, as recorded on tape, produced flux values up to some 8 to 10 dB beyond the 1 percent distortion level, in other words, far in excess of the 3 percent distortion point? Yes, because in 1965 the NAB standard for reel-to-reel recordings has the following to say in a footnote to section 2.04, which relates to the standard reference program level: "It is well established that at least 10 dB margin is required between the sine wave load handling capacity of a system and the level of program material as measured by a standard volume indicator." The NAB standard reference level is described in section 2.03 with a footnote which reads as follows: "The recording was made... at an output level 8 dB below that which produces 3 percent third-harmonic distortion." (This is not contradictory to the above statement because it simply defines a level of tape magnetization which is to serve as a reference.) So, where do we go from here? ==THE AMERICAN REFERENCE FLUX== Fortunately, John McKnight in the United States seemed to have been bothered by this lack of a precise value for recorded tape flux. As a consequence, he investigated this situation and prepared his findings for publication in the Journal of the Audio Engineering Society.[2] A reference flux of 100 nWb/m is mentioned or suggested in that investigation, and one reads for the first time 210 nWb/m for the earlier discussed Operating Level and 165 nWb/m for the NAB Standard Reference Level. Later on, these values were downward corrected slightly, and from a 1972 data sheet of a manufacturer of calibration tapes, one can read 185 nWb/m for the Operating Level and 150 nWb/m for the NAB Reference Level. At this point, we should pause to take a closer look at the units of measurement. ==UNITS OF MEASUREMENT== NanoWeber-per-meter is the value of fluxivity that would be measured if the tape was 1 meter (or approximately 39 3/8 inches wide. Reducing this to a more realistic width, namely 1mm (or 39 mil), the unit became picoWeber-per-millimeter, which was 0.1 milliMaxwell per millimeter in the days before the ST units came into force. In the case of the NAB Reference Level, the result is 15 mM/mm, which explains one of the values mentioned in the title of this article. Since we are already doing some calculations, let's look at the previously mentioned German reference of 200 milliMaxwell for 1/4-inch tape. If we divide that figure by the metric equivalent of 1/4 inch, which is 6.25 mm (tapes today are 6.3mm wide), then we get the figure of 32 mM/mm. Converting this to nanoWebers, we arrive at the standard 320 nWb/m. It may be worth mentioning at this point that in a comparison of U.S. and European levels one must be aware of the fact that the ANSI S 4.6 method of measuring remanent flux yields a value which is lower by 0.8 dB, as compared with a measurement performed in accordance with DIN 45 520. In practice, this means that when comparing calibration tapes of U.S. and European origin, the U.S. tape will yield a higher signal level because what is 200 nWb/m in the U.S. would measure 220 nWb/m in Europe. (This also explains the previously cited downward correction from 165 to 150 nWb/m.) ==STEREO-MONO COMPATIBILITY== After this digression into levels and their history, let's continue on. Magnetic oxides were improved over the years, making higher levels of magnetization possible without adversely affecting distortion performance. This made it feasible to raise the operating level (0 VU) to 250 nWb/m for the so-called High Output tapes. In Europe (more precisely in Germany), the advent of stereo made those exacting engineers reach for their slide rules, because stereo/mono level compatibility was their goal. Music productions were already recorded in stereo, yet broadcasts were still in mono. Such a stereo recording, when played back on a full track head, did not produce the same signal level as that which resulted when playing a mono recording; there was some unused, unmagnetized "land" between the stereo tracks, and left and right signals were not adding up algebraically. One can live with reduced cross-talk performance in stereo, so the tracks were widened until they were spaced only 0.75mm apart, making each track 2.75mm wide. As a result of this, the core sections of the head spread out at an angle to accommodate the windings. With this, the Butterfly Head was born (see FIGURE 1). [[File:Butterflyhead.gif|frame|none|Figure 1. Butterfly head]] The tape's width was utilized to a possible maximum, but stereo/mono level compatibility was still not reached. A few quick calculations and one can see that a stereo recording has to be modulated to 514 nWb/m in order to produce the same signal level as that which is obtained from a 320 nWb/m mono recording when playing the stereo tape on a monophonic reproducer. Total flux, mono on 1/4-inch (6.25mm) tape: 320 nWb/m x 6.25 = 2000 nWb/m Stereo played on full track head: [[File:Formula.gif|Formula.gif]] The goal was reached: The fader on the mixing desk did not have to be moved, regardless of whether mono or stereo recordings were played! At the time it was a bit strange, perhaps, to see blank tape appearing on the market which was labelled "stereo," though this simply meant that such a tape could be modulated to the higher stereo level without any increase in distortion. Stereo/mono compatibility - which is not of much interest anymore - is thus explained, but what about universal compatibility of recorded levels in general? ==VU VS. PPM AND PEAK FLUXIVITY== In America the VU-meter is still favored while in Europe the peak program meter (PPM) is predominant. The performance characteristics of the latter are described and specified in IEC 280-10 and in DIN 45 506. It is a quick-acting meter, and because of this, it is also called a "quasi peak-reading meter." However, as suggested by the word quasi, it is not a true peak-indicating device. A closer examination of its characteristic behavior suggests that short modulation peaks may overshoot by 1 to 4 dB.[3] A graphic presentation (FIGURE 2) of the maximum output level performance (MOL) of various tapes, including the most modern oxides, shows how tape performance has improved over the years. The point of maximum modulation, which is universally considered to be the level at which the third-harmonic distortion content measures 3 percent,[4] has shifted gradually to higher flux values, with 1,200 nWb/m being reached by at least one state-of-the-art tape. This explains the second figure in the title. Quite a wide range from the NAB reference of 150 nWb/m via the high-output operating reference to the German DIN levels for mono and for stereo, up to the MOL which is possible today. [[File:mol.gif|frame|none|Figure 2. Maximum Output Level (MOL) performance of magnetic recording tapes at 15ips. O= Theoretical peak flux values when aligning VU meter or PPM as described in text The dashed line (1955} represents the performance of the old U.S tape if flux values were measured in accordance with DIN.]] Attempts to establish references of even figures have been repeatedly made. For example, there is the EIA standard RS-400/1972 containing a reference to CCIR 79-1/1966 at which time the value of 100 nWb/m was recommended, and in more recent times, one finds 400 nWb/m mentioned in a newer EIA standard. But all this is of little help to a studio's maintenance engineer when faced with the decision of how he should calibrate his level meters. So, in analyzing this historical retrospect it comes almost as an automatic conclusion that 250 nWb/m (or even 320 nWb/m) would be a good reference for calibrating a VU-meter to its 0 VU reference deflection, as it would allow the modulation peaks to reach up to 800 or 1,000 nWb/m. In the case of a quasi peak-reading meter or PPM, however, the 510 nWb/m (or 500 for simplicity's sake, being twice 250) would be an equally good reference because its assumed 4 dB overshoot would again result in a peak magnetization in the range of 800 nWb/m, still well below the accepted MOL of 3 percent third-harmonic distortion. It's up to the individual engineer's discretion, of course, as to how hard he intends to drive his tape into saturation. It should be borne in mind, however, that for every dB gained in signal-to-noise, one must pay with a disproportional increase in distortion, a fact which was discovered long ago by a pioneer in the development of new recording techniques.[5] Analog recording may still be around for a while, and so it is hoped that useful conclusions can be drawn from this article which help to ensure that the inherent quality of analog is not given away unwisely, as may all too often be the case. [[File:flux.gif|frame|none|Output Level vs. Flux (taken from the Studer 820 Service-Manual)]] ==References== 1. Krones, Dr. F. "Herstellung und elektroakustische Eigenschaften der AGFA Magnetbander, Filme und Bezugsbänder." Sonderdruck aus den Forschungslaboratorien der AGFA Leverkusen. Band I. (Nov. 1955), Seite 304. 2. McKnight. John G. "Absolute Flux and Frequency Response Characteristics in Magnetic Recording." Preprint 447. 31st AES Convention. Oct. 1966. Published in revised form: Journal of SMPTE Vol. 78. (June 1969), pp 457-472. 3. Silver. Sidney L. "VU-Meters vs Peak Program Meters." db (Jan. 1980). pp 46-49. 4. DIN 45 511. "IEC Draft 94-5." NAB Magnetic Recording And Reproducing Standards (1965), Section 2.11: Distortion. 5. Langevin, Robert Z. "Intermodulation Distortion in Tape Recording." Journal AES (July 1963). Vol. 11. pp 270-278. aus: db magazine July 1984 pp 36-38 4bac1475167ff3a828e2861ffb0db52efbe74d86 0 587 2581 2580 2020-09-30T12:03:26Z Pvdm 2 wikitext text/x-wiki To send email that is in fixed font you can use: <pre> # (echo "Subject: bla"; echo "MIME-Version: 1.0"; echo "Content-Type: text/html"; echo "Content-Disposition: inline"; echo '<html><body><pre>The code element<SLASHpre></body></html>') | sendmail joop@hotmail.com </pre> Mind the /pre here. 1898959c0b52f336fbabff5ec570d56c9c6b36aa 0 485 2583 2333 2021-01-26T09:13:58Z Pvdm 2 wikitext text/x-wiki <pre> It takes alot more power to erase DV tapes than what Hand Held Radio Shack Bulk Tape Erasers can handle. Here's a chart showing the power needed to erase DV Tapes. (It takes 1700 Oersteds to erase DV tapes.) Coercivity is the property of a given magnetic pigment to resist changes in magnetic orientation or re-orientation (= "erasure"). It is defined by the level of the magnetic field needed for (re-)orientation, expressed in Oersted (Oe). The higher the coercivity, the higher the resistance of magnetic information to re-orientation (or erasure) by external magnetic fields. AUDIO Tapes Oersteds ================================== 350 Oersteds = 1/2", 1" and 2" 350 Oersteds = Cartridge 350 Oersteds = Sep.mag.35mm film 365 Oersteds = Voice logging reel 1/2", 1" 450 Oersteds = Compact cassette ferric (IEC Type I) 450 Oersteds = Compact cassette chrome (IEC Type II) 680 Oersteds = 1/4", 1/2" digital audio reel 745 Oersteds = 3/4" digital audio cassette 10/750 Oersteds = Pancake various 700 Oersteds = DCC 930 Oersteds = ADAT 1440 Oersteds = RDAT COMPUTER/Data Tapes Oersteds ================================== 300/700/1500 Oersteds = Floppy diskette 51/4",31/2" 550 Oersteds = PC,Mini, Hard disk 310 Oersteds = Main-frame Spool 1/2" 550/650 Oersteds = Cartridge 1500 Oersteds = TK50 etc. 700 Oersteds = DCRSI cassette 310 Oersteds = Reel 1/2", 1" 675/750 Oersteds = Cassette 1050/1500 Oersteds = 8mm/4mm 1440 Oersteds = DAT-R 550 Oersteds = Cartridge 3480, DC600A 1900 Oersteds = Digital backup cartridge VIDEO Tapes Oersteds ================================== 750 Oersteds = Reel 1"`B'and`C' format 300 Oersteds = 2" 675/750 Oersteds = VHS pancake 2100 Oersteds = Mirror master 675/700 Oersteds = Cassette VHS 710 Oersteds = Beta 1000 Oersteds = SVHS 1050/1500 Oersteds = Hi8 630 Oersteds = U-matic 745 Oersteds = U-matic SP 1700 Oersteds = Beta SP, MII 850 Oersteds = D-1 1700 Oersteds = D-2, D-3 Digital 1700 Oersteds = Digital Betacam, D5 Digital 1700 Oersteds = DV, DVC, DVCAM, DVC PRO SECURITY formats Oersteds ================================== 600 Oersteds = Credit card 600 Oersteds = Library ticket 600/3500 Oersteds = Rail/Air ticket 600 Oersteds = Hotel door lock (INFO FROM: <a href="http://www.weircliffe.co.uk/degaussi.htm">Weircliffe</a>) Here's something interesting: ============================== From: Art Munson <artmuns@tape.com> Subject: Degaussing, erasing and magnetism Date: Tue, 27 Aug 1996 11:58:42 -0500 (CDT) Degaussing, Erasing and Magnetism --------------------------------- A lot of folks have asked about degaussing (erasing) media and particularly DAT tapes, so here's some info you might find helpful. Gauss: A unit of measurement of magnetic flux density produced by a magnetic force (coils). Gauss is a measurement of coil strength. Oersted: A unit of magnetic intensity of a magnetic field in a vacuum. Oersted is a measurement applied to media. A 4mm DAT tape has a magnetic field strength of approximately 1500 oersteds. Coercivity: The amount of applied magnetic field (of opposite polarity) required to reduce magnetic induction to zero. The ease or difficulty by which magnetic media can be de-magnetized. A 4mm DAT tape is a high coercivity tape. So: 1.) The higher the oersted rating, the more energy needed to *properly* demagnetize it. 2.) In order to degauss (erase) a magnetic tape, a magnetic force (gauss) of 2 2/3 to 5 times greater than that of the media to be degaussed must be created. In other words to demagnetize a media of a given oersted rating, it will take 2 2/3 to 5 times the amount of energy. 3.) A 1500 oersted tape would need a magnetic field strength in the neighborhood of at least 3000 gauss in order to *properly* erase it. Hope this helps and thanks to David Partridge for his input. There is a hand held DAT degausser available, with an oersted rating of 2800, that lists for $169. Please give a call at 800-321-5738 if you are interested. Art * Cassette House * e-mail:artmuns@tape.com * DAT tape - CDR's - Cassettes * web page http://www.tape.com/ch * 800-321-5738 "I will use no track before its time" (INFO FROM: <a href="http://www.solorb.com/dat-heads/digests/V2.900/D921">DAT Digest</a>) ================================== Radio Shack's High Power Gauss Field is 800 oersteds. <a href="http://support.radioshack.com/support_video/doc14/14741.htm">Specs</a> ================================== So as you can see, degaussing DV tapes can be done with the right equipment. Let's see...to erase a DV tape of 1700 Oersteds I need a degausser that can handle 3400 Oersteds. Hmmm, The Radio Shack High Power Bulk Tape Eraser handles 800 Oersteds. No wonder it didn't work. </pre> c3d1003c3cf4303cb2314c32fd29fab756bf4a5b 0 39 2586 2347 2021-02-23T19:52:29Z Pvdm 2 /* Apache */ wikitext text/x-wiki ==Apache== *[[compare Apache conf files and Nginx conf files]] *[[joomla migratie 1.x naar 1.5]] *[[embed video in html5]] *[[certificate renewal apache]] 54174d26b8f5e568eedb86922303948cebed3d3a 0 553 2589 2425 2021-02-26T13:30:15Z Pvdm 2 wikitext text/x-wiki This page is also for the Philips DCC730. They have the same tapemechanism. =specs= * snaren: ** capstansnaar lengte dubbelgevouwen is ongeveer 150 mm, of iets korter. breedte 3mm, dikte 0,5 mm. <pre> straal | radius : 48mm omtrek | circumference : 300mm diameter | diameter: 95mm plat | flat lenght : 150mm </pre> ** een 2e én 3e exemplaar hadden dubbelgevouwen lengte van 155 mm. ** ladesnaar lengte dubbelgevouwen 98mm, vierkant 1,3mm breed. * aandrukrol: 13 x 6 mm as: 2 mm * Verder moet je de voeding nakijken, soldeerverbindingen van o.a. de spanningsregelaars. * aansluitingen bij de tulpstekers. Er kunnen printbreuken zijn. =english= *belt ** capstanbelt lenght folded flat approx. 150 mm, or a little bit shorter. Width 3 mm, thick 0,5 mm. ** traybelt length folded flat 98 mm, square 1,3 mm width, * pinch roller: 13 x 6 mm, axis: 2 mm. * Check power supply; solderings * check connections at rca audio plugs. possible board fractures. =initialize a tape= Initialize new tapes, or make them new again: For DCC730 & 951: REWIND, REC SELECT/PAUSE =track numbering= According to the DCC specification, on side B a new track number starts. So, when recording from CD, and a track overflows from side A, a new tracknumber will be generated at the start of side B. Therefor, all tracknumber on side B will be the original numbering +1 =clean head is displayed= 'Clean Head' is displayed when * 8 hrs of ACC is played * 2 channels or more on DCC tape not detected by DCC head for more than 3 seconds. In case CLEAN HEAD indication was caused by a temporary bad head-tape contact, the message will disappear after pressing TIME or TEXT key. =Enter Service Test Program= Press 2 keys simultaneously PLAY+STOP and switch power on. =ERROR NUMBER SURVEY= These numbers will be displayed sometimes when an error occurs. The numbers have the following meaning: <pre> 00: No error 01: Deck failed The requested command could not be executed because of a malfunctioning of the mechanics. 02: Tray blocked This error is issued when the tray has been blocked, although the tray might be moving out again due to this fact. The blocked indication will hence occur very short in the tray status message and could be missed. 03: Tray pulled open During normal operation the tape drive module has sensed that the tray loader is forced to the open state by the user. 04: Invalid parameter The parameter going with the last received command is unknown or out of range. 05: No cassette The command can not be executed since there is no cassette loaded. 06: Digital Audio input but of lock or missing carrier During recording from a digital input, no input signal is detected. When continuing the recording, undefined data will be recorded which may lead to unpredictable audio during playback. The DDU module will refuse to continue the recording. 07: Digital Audio input has Professional class (unsupported) During recording from a digital input, a professional source may be detected which is not supported by the DDU module, hence the module will refuse to record from this source. 08: Digital Audio input has non-audio format During recording from a digital input, the input data may contain computer data instead of audio. The DDU module will refuse to continue the recording. 09: Copy right protection violation (SCMS) During recording from a digital input, which contains user audio data but which is copyright protected, the DDU module will refuse to continue the recording. 10: Internal DCC chip error There has an error occurred within the DCC chips on the DDU digital module. When this error persists over a longer period of time, please consult your nearest service officer. 11: Record attempted on write protected tape A record or auxiliary record or record-pause command is issued while the loaded cassette is write protected or is an A00. The DDU module will refuse to record on such a tape. 12: Non existent search target The target to search for does not exist on the currently loaded cassette. e.g. search for track number 20 while the tape only contains 12 tracks. 13: Invalid command received The command which was received is not allowed in this context. 14: Setting not allowed This error message will be returned when the DDU module is performing a TOG search and a next_previous_count is downloaded. 15: Command overrun The DDU module has received to many state changing commands in a row to handle. This error occurs whenever a command is received while another command is still waiting for execution. The DDU module will not store a queue of received commands. 16: Signature not yet loaded The record command will only be accepted by the DDU module after the setmakers signature has been loaded. This will make it possible to identify the recording set of each DCC cassette. 17: Unreliable TOC During the process of TOC search the DDU module found out that the contents of the TOC does not match the contents of the tape. The search command should be repeated using relative search. 18: Search target could not be found The requested search target was valid but could not be found, e.g. a direct track search after track number 5 on a super-user tape while track number 5 was removed by after-reoording, or an append search on a full tape. 19: Marker writing not allowed A request for a marker can be rejected because of the fact that the last recorded marker is not yet 3 tape frames past or a marker is currently being written or the tape is write protected. Also when the requested marker is out of context (lead_in A on side B or reverse maker on side B this error occurs. 20: Not Used. 21: No track numbers on this tape Attempt to do a track search on a tape with notrack numbers, e,g, search track number 10 on a non-super user tape. Note that a search for track number 1 will always be honoured. 22: No proper super-user tape The renumber function could not detect a marker on this super user tape or the renumber function was called on a user tape. 23: No TOC available A direct access search has been requested on a super—user tape which does not have a valid TOC. This search requests can not be honoured. 24: Sector not allowed Not allowed to change sector in this mode or a sector is requested which is not on the tape, e.g‘. sector D on a 2-sector tape. 25: No user characters loaded An attempt to record user characters while these are not yet loaded. 26: Clean head The reproduction of the audio is bad due to dirt on the head. The user should clean it. 27: Marker may not be removed Attempt to erase a temporary reverse marker or the first start marker on the tape. 28: No search from virgin A search action can not start from a virgin tape position. 29: Tape drive does not respond This error occurs when the digital module can not communicate with the tape drive module. 30: Tape fault on tape broken/blocked. 31: Power down detected by tape drive module. </pre> 5c32e2080c06b8759df9470e8e63bf8fb634d8be 0 513 2592 2591 2021-03-15T13:39:30Z Pvdm 2 /* Chromium */ wikitext text/x-wiki =firewall= ==Allow Multicast in Firewalld== sudo firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -m udp -p udp -m pkttype --pkt-type multicast -j ACCEPT ==open ports== * tcp 8008-8009 * udp 32768-61000 =Chromium= The native "Cast..." does not work until you enable this flag below. Once its enabled, it works perfect, no need for any extension. chrome://flags/#load-media-router-component-extension set to enabled. also Cast Media Route Provider tested on Version 60.0.3112.113 (openSUSE Build) (64-bit) =Command line= ==catt== $ ~/.local/bin/catt -d Kitchen cast -s ./Men.in.Black.2.2002.1080p.BluRay.H264.AAC-RARBG.srt ./Men.in.Black.2.2002.1080p.BluRay.H264.AAC-RARBG.mp4 $ ~/.local/bin/catt -d "Kitchen" cast "https://www.youtube.com/watch?v=dQw4w9WgXcQ" 4e8c26f5e574bcacedad97ac45bb6ab353888b35 0 589 2594 2021-03-16T11:14:33Z Pvdm 2 Created page with "*[[video output info]]" wikitext text/x-wiki *[[video output info]] 40e9dda7713de09befcbf817f12361ee939ff23f 0 591 2596 2595 2021-03-16T11:17:51Z Pvdm 2 wikitext text/x-wiki Depending on the age, old consoles (and computers) output a worse video signal (quality-wise) than what the internal components actually produce. This was needed to be able to connect to TVs at the time. For example, the oldest output format is RF, which was connected to the antenna of TVs. While this is still fine for some people, others prefer the best possible signal, which means feeding the color and sync signals individually to the monitor. The quality ladder from worst to best is: *RF *composite video *S-Video *component/YPbPr *RGBS/RGBHV. The higher the quality, the more individual wires you have. While RF mixes everything including sound into one signal (hence one wire), with RGBHV you have 5 video + 2 sound wires. The best an unmodified C64 can output is S-Video (2 wires for video signal and 1 for mono sound), hence to get something even better you need a special modification board that then produces component or RGBS video signals (depending on the settings). Of course, this is all very simplified, nowadays, for some old computers/consoles you even have digital output modifications available that you can connect e.g. via HDMI. It is this one (open source): https://github.com/c0pperdragon/C64-Video-Enhancement You can buy pre-built ones e.g. here: https://videogameperfection.com/products/commodore-component-video/ These ship with an older firmware (2.6) though, I had to update (2.10) mine to get it working with my older C64 version. 3f90f318eaf38fc72a6f772371dd2f0020191b24 0 10 2601 2297 2021-06-05T08:44:51Z Pvdm 2 wikitext text/x-wiki *[[kde over ssh]] *[[Snapper]] *[[Snapper PvdM]] *[[How to start qbittorrent]] *[[How to make the screen brightness keys work again in KDE]] *[[bluetooth]] *[[journald]] *[[systemd journal log file setting]] *[[KDE apps look ugly and missing icons over ssh]] *[[KDE font settings]] *[[things to clean up before doing large copy of entire system]] *[[installing spotify on openSUSE 12.3]] *[[fixing desktop freezes on large copies]] *[[A guide to using systemd]] *[[Things to do after a fresh installation of openSUSE 12.1]] *[[Things to do after a fresh installation of openSUSE 11.4]] *[[improve the font rendering - using subpixel hinting]] *[[How to have the latest kernel in openSUSE]] *[[Install openSUSE via SSH]] * [[Upgrading to KDE 4.5.0 on OS11.3]] * [[Upgrading the system to a newer version using zypper dup]] * [[Things to do after a fresh installation of OpenSUSE]] * [[Repositories in openSUSE - The current state]] * [[Fixing CUPS login problems on SUSE]] * [[Speed up tips for (suse) linux installation]] * [[Problem w/ ZEN/rug/rpm database]] * [[installatie openftd in OpenSUSE 10.3]] * [[Speedup Package Management]] <- on opensuse 10.x * [[Install a PXE boot server on 11.1]] * [[monitor an OpenSUSE system]] * [[Install all updates using zypper]] * [[Install ATI/NVIDIA drivers in Opensuse 11]] * [[How to locally cache zypper update files]] * [[Check and install media formats]] * [[boot options in suse grub]] * [[openSUSE 11.1: enable the KDE4.2 repos]] * [[Stop SSH brute force attacks]] * [[codecs issues 11.1]] * [[Upgrade openSUSE 10.3 to 11.1 while the system is running using zypper dup]] * [[Best way to use GRUB in a multiboot system]] * [[How to resue your system when the kernel won't boot]] * [[Fix suspend to RAM on a HP8530p EliteBook on OpenSUSE 11.2]] * [[OpenSUSE 11.2 MP3 playback in Amarok]] * [[Updating OpenSUSE in-place using zypper dup]] * [[KDE openSUSE repositories explained]] * [[Installation of openfire jabber xmpp server on openSUSE server]] * [[How to toggle compositing in KDE on the CLI command line]] * [[KDE4.4 issues openSUSE 11.2]] * [[Starting chromium as default browser in thunderbird]] *[[IRC channel commands]] *[[icedtea error on starting java in browser]] *[[vlc crashes when switching interface to qt4]] *[[smt]] 9a2aeaf01bc9e165fc80d2b2229bcbf89419d76d 0 592 2602 2021-06-05T08:45:18Z Pvdm 2 Created page with " $ export XDG_CURRENT_DESKTOP=kde $ dolphin" wikitext text/x-wiki $ export XDG_CURRENT_DESKTOP=kde $ dolphin fb56375b44da80d08ecc1b286e02ce922ddf9485 0 103 2607 2606 2021-06-11T15:28:16Z Pvdm 2 /* update 20210611 */ wikitext text/x-wiki =update 20210611 Best Version:= wget -m https:// =original= If you want to make a dump of a website, then you can do: /usr/bin/wget -q --convert-links -E -m http://website.nu.com.mp3 wget --progress=bar --convert-links -E -m ftp://ftp.studer.ch/Public/ Actually, to download a single page and all its requisites (even if they exist on separate websites), and make sure the lot displays properly locally, this author likes to use a few options in addition to -p: wget -E -H -k -K -p http://<site>/<document> -E adjust extention ??? -H also download from foreign hosts -p download all page requisites '''PvdM version:''' wget -r -k -K -p http:// -r recursive -k convert links -K backup converted 4adade21692a6cb9e79faacadfc61670fdec796b 0 427 2608 1559 2021-06-26T09:35:39Z Pvdm 2 wikitext text/x-wiki I had several bad experiences losing my data in my life. Sometimes because of the hardware, sometimes because of my stupidness or inexperience. At least, it learned to be careful. I backup my data regularly, and on several support concerning the important ones. I sometimes back up my primary partition, where the system is set. If my drive crashed, I want to recover quickly a system without having to reinstall hundreds of applications. I have used several times Partimage and was satisfied. But now I tend to use dd, which basically do the same thing in just one line. The advantage is that it is by default on any Linux distribution. To back it up on an usb disk : $ sudo dd if=/dev/hda1 | gzip -v | dd of=/media/usbdisk/backup_hda1.gz To backup my home and other data partitions, I just copy the files manually, it is faster and there is no need to backup such a thing as the boot sector. But of course you could use the same command above. When you wish to restore the partition to a new hard drive, just : $ zcat /mnt/hdb5/sauvegarde.gz | dd of=/dev/hda1 To do that, you will have probably booted on a live CD Linux as Knoppix to restore the crashed system. In any case, don’t overwrite the system you just booted on ! One tip if you want to back up only the boot sector : $ sudo dd if=/dev/hda of=/home/secteur_boot.dd bs=512 count=1 And to restore : $ sudo dd if=/home/secteur_boot.dd of=/dev/hda bs=512 count=1 =Advanced options= oflag=direct,sync for writing to slow devices such as SD cards, oflag=direct keeps it from filling up the process's memory with the backlogged output, and oflag=sync keeps it from filling up the kernel's memory. direct is a good idea if you want to avoid buffering on the write end, but sync will severely degrade performance if the drive you're writing to does its own buffering. It will force every write to flush the drive's buffer too before moving on. also: status=progress 603b8ac981683bc2fea3a3b6986d3ff3c200c0d7 0 593 2625 2624 2021-10-26T18:02:14Z Pvdm 2 wikitext text/x-wiki Pulseaudio is usually installed with default options to make it work with most hardware. But settings can be tuned for better sound-quality. Adjust the following settings in your daemon.conf: <pre> resample-method = soxr-vhq avoid-resampling = yes flat-volumes = no high-priority = yes realtime-scheduling = yes default-sample-channels = 2 default-sample-rate = 96000 alternate-sample-rate = 48000 default-sample-format = float32le </pre> *The two sample rate settings can be adjusted to suit your hardware configuration. *Also the sample-format can also be u8, s16le, s16be, s24le, s24be, s24-32le, s24-32be, s32le, s32be float32le, float32be, ulaw, alaw. * resample-method can be <pre> trivial speex-float-0 speex-float-1 speex-float-2 speex-float-3 speex-float-4 speex-float-5 speex-float-6 speex-float-7 speex-float-8 speex-float-9 speex-float-10 speex-fixed-0 speex-fixed-1 speex-fixed-2 speex-fixed-3 speex-fixed-4 speex-fixed-5 speex-fixed-6 speex-fixed-7 speex-fixed-8 speex-fixed-9 speex-fixed-10 ffmpeg auto copy peaks soxr-mq soxr-hq soxr-vhq </pre> bd3d4e1c9eb3765b1e1d9f501dd075befe5668d7 0 594 2627 2021-11-24T13:45:58Z Pvdm 2 Created page with " # rsync -aAXv --exclude 'data' --exclude 'mnt' --exclude 'proc' --exclude 'sys' --exclude 'dev' --exclude 'run' /* /mnt/mmcblk/3/" wikitext text/x-wiki # rsync -aAXv --exclude 'data' --exclude 'mnt' --exclude 'proc' --exclude 'sys' --exclude 'dev' --exclude 'run' /* /mnt/mmcblk/3/ 70385c28977ade5cd8e9f8219dcb329f85f6bbdd 0 450 2629 2411 2021-12-03T18:05:21Z Pvdm 2 wikitext text/x-wiki trap ctrl-c in terminal: trap 'play -nq synth sin 1000 trim 0 0.35 vol 0.5 2>/dev/null' INT watch if a website changes: while :;do curl -Ls "X\.com"|md5sum;sleep 5m;done|awk '{if(NR>1&&l!=$1){system("echo the site changed|mail -s NOTIFY you@isp\.net");};l=$1}' scan pdf to file. first extract the pages and ocr them, then make one doc pdfimages -tiff input.pdf plaatje for i in *.tif; do tesseract $i tempje-$i; done cat tempje-plaatje-0*.txt >> docje.txt ps ax -o state -o ppid | awk '$1=="Z"{print $2}' | xargs kill -9 # Kill all #zombies on the system. ps aux |tail -n+2 |sort -nrk4 |head -$(($(tput lines)-1)) |cut -c 1-$(tput cols) # Display top RAM using processes. ethtool -p eth0 # Blink eth0's LED so you can find it in the rat's next of server cables. Ctrl-C to stop. find . -xdev -ls | sort -n -k 7 | tail -5 # Quickly find the largest 5 files in the CWD tree without crossing filesystem boundaries. for f in *; do b=$(echo "$f" | tr '[A-Z]' '[a-z]'); mv "$f" "$b"; done # Lower case all files in a folder. rpm -qf $( which lspci ) # Pass the output of which (showing path to lspci) into rpm's -qf, which tells you the pkg. rename -v 's/^([0-9])_/0\1_/' *.flac # Rename all single leading digit flac files so that they have a padding 0 for easier sorting. ps aux | awk '{if ($8=="Z") { print $2 }}'# On Linux, print out a list of the process IDs that are in the zombie state. exiv2 -k -F rename *.jpg # Use the exiv2 EXIF program to rename your jpg files according to their exif date/time data. curl http://wttr.in/castricum # see weatherforecast finger amsterdam@graph.no rpm -qa --queryformat "%{NAME} %{INSTALLTIME:date}\n" | grep "Nov 2015" # In RPM, determine which packages where installed in Nov 2015. echo "wall \"hallo\""| at 11:48 2016-02-27 # execute a command at a certain time and date ls -la "$(find . -type f -printf '%T@ %p\n' | sort -n | tail -1 | cut -f2- -d" ")" # show the most recent file in subtree grep -Ev "((accept|drop|reject)log|ftpd)" /var/log/messages | less # Yes! You can do nested grouping in extended regexes. With Bash history, `^str1^str2^` will repeat the previous command replacing `str1` by `str2`, so echo 1223 ^2^4^ The #Bash has the notion of "integer" variable: <pre>declare A=1; declare -i B=2 A+=3; B+=4 echo $A $B ⇒ 13 6</pre> sort -t, -k5nr data.csv | less # Sort data.csv by the 5th column's numeric values in descending order. Play a sound if you get an unsuccessful return code from last command. PROMPT_COMMAND='[ $? -ne 0 ] && play -qn synth sin G3 trim 0 0.1' Command used by P2V process: tar --one-file-system --sparse -C / -cf - . Show error warn and criticals in color: # tail -f "foo.log"|egrep --line-buffered --color=auto 'ERROR|WARN|CRITICAL$ Very good overview of open ports and their programs: # lsof -Pan -i tcp -i udp To remove the hashtag parameter in a file and add the line if not exist; thus making sure the parameter is always present and enabled: # grep -qi 'ForwardToSyslog' /etc/systemd/journald.conf && sed -i 's/#ForwardToSyslog.*/ForwardToSyslog=Yes/' /etc/systemd/journald.conf || echo 'ForwardToSyslog=Yes' >> /etc/systemd/journald.conf 17f26e4de7cb97c2a067716499e64aa6cb8932a4 0 149 2632 2631 2021-12-17T13:36:43Z Pvdm 2 /* jump */ wikitext text/x-wiki If you're spending your weeks in the timeline, you'll want to know a more efficient way of navigating it. There are all the usual video editing conventions in Kdenlive, albeit with some variation in keyboard assignments. =jkl= The now classic and ubiquitous "jkl" keyboard sequence is also present in Kdenlive. To play your timeline, you may press "l" (lowercase L) once for standard speed, "ll" for double speed, "lll" for triple speed. "K" stops playback. Press "j" for reverse playback, "jj" for double speed reverse, and "jjj" for triple speed reverse. =move by frame= You can also move by frame or by second. The left or right arrow will advance or rewind by one frame; shift-leftArrow or shift-rightArrow will move forward or back by one second. =jump= To move your playhead to the beginning of a video region, use the Home key; for the end of the region, use End. To move along the timeline by splices, use Alt-leftArrow or Alt-rightArrow. And finally, you can jump to the beginning or end of the Timeline with control-Home or control-End. By using these navigational tools, you'll find that for very long stretches of video editing, you won't need to bother with your mouse, which, as any Unix guru knows, is the real key to efficiency. =edit= cut: shift-r fd7c302e28f1c0a070aebc07d6a9884f7eff37dc 0 595 2635 2022-01-26T20:09:37Z Pvdm 2 Created page with "put in .bashrc or bash.bashrc.local <pre> # fix bash history export HISTCONTROL=ignoredups:erasedups # no duplicate entries export HISTSIZE=100000 # big big..." wikitext text/x-wiki put in .bashrc or bash.bashrc.local <pre> # fix bash history export HISTCONTROL=ignoredups:erasedups # no duplicate entries export HISTSIZE=100000 # big big history export HISTFILESIZE=100000 # big big history shopt -s histappend # append to history, don't overwrite it # Save and reload the history after each command finishes export PROMPT_COMMAND="history -a; history -c; history -r; $PROMPT_COMMAND" # end fix bash 14c55456d7f138bf730daadc6322c0dc1fda7f57 0 451 2638 1864 2022-02-06T21:11:25Z Pvdm 2 wikitext text/x-wiki Elitebook 8570 ???? screen: Screen 0: minimum 320 x 200, current '''1600 x 900,''' maximum 16384 x 16384 LVDS connected primary 1600x900+0+0 (normal left inverted right x axis y axis) '''345mm x 194mm ''' diameter: '''15,8''' inch dpi: '''116''' SSD: mtfddak256mam-1k12 81a239a27d06c09fafc8c76d18f7a5381579c580 0 596 2641 2640 2022-02-26T14:53:49Z Pvdm 2 wikitext text/x-wiki <pre>lapx: # lspci -nnk |grep -A3 VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] DeviceName: 0 Subsystem: Hewlett-Packard Company Device [103c:17a9] Kernel driver in use: radeon lesie:~ # lspci -nnk |grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Subsystem: Lenovo Device [17aa:396b] Kernel driver in use: i915 Kernel modules: i915 amd64:~ # lspci -nnk |grep -A3 VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] Subsystem: ASRock Incorporation Device [1849:990e] Kernel driver in use: radeon Kernel modules: radeon 49c1d880337bcfc211eae991195bbdc80c775742 0 598 2647 2646 2022-03-27T09:55:24Z Pvdm 2 wikitext text/x-wiki = Specifications = <div style="color:#000080;margin-left:0cm;margin-right:0cm;">Dell™ Latitude™ D610 User's Guide</div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Processor''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Processor type | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Intel® Pentium® M |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | L1 cache | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 32-KB instruction and 32-KB write-back data cache |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | L2 cache | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 2 MB |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | External bus frequency | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 533 MHz |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''System Information''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | System chipset | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Intel 915GM (integrated video), ICH60M, or Intel 915PM (discrete video), ICH60M |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Processor Side Data bus width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 64 bits |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | DRAM bus width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | DDR2 dual channel 400 MHz/533 MHz (independent 64-bit memory data channels) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Processor address bus width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 32 bits |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Flash EPROM | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 1 MB |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Graphics bus | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | integrated |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | PCI bus | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 32 bits |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''PC Card''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | CardBus controller | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Texas Instruments PCI 6515 CardBus controller (support for USB express cards through adapter in CardBus slot) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | PC Card connector | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | one (supports one Type I or Type II card) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Cards supported | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 3.3 V and 5 V |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | PC Card connector size | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 68 pins |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Data width (maximum) | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | PCMCIA 16 bitsCardBus 32 bits |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Memory''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Memory module connector | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | two user-accessible SODIMM sockets |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Memory module capacities | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 256 MB, 512 MB, and 1 GB |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Memory type | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 400 MHz or 533 MHz 1.8-V DDR2 SDRAM SODIMM |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Minimum memory | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 256 MB |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Maximum memory | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 2 GB |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Ports and Connectors''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Audio | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | microphone connector, stereo headphone/speakers connector |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Infrared | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | sensor compatible with IrDA Standard 1.1 (Fast IR) and IrDA Standard 1.0 (Slow IR) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Mini PCI | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Type IIIA Mini PCI card slot |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Modem | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | RJ-11 port |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Network adapter | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | RJ-45 port |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Parallel | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 25-hole connector; unidirectional, bidirectional, or ECP |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Serial | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 9-pin connector; 16550C-compatible,16-byte buffer connector |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | S-video TV-out | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 7-pin mini-DIN connector (optional S-video to composite video adapter cable) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | USB | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 4-pin USB 2.0-compliant connector |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 15-hole connector |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Communications''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Modem: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Type | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | v.92 56K MDC (optional) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Controller | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | softmodem |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Interface | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | internal AC'97 bus |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Network adapter | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 10/100/1000 Ethernet LAN on system board |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Wireless | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | internal Mini PCI Wi-Fi (802.11b, 802.11b/g, or 802.11a/b/g) and Bluetooth® wireless technology (optional) |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Video''' |- style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | <span style="color:#000080;">'''NOTE:&nbsp;'''</span>Your Dell™ Latitude™ D610 computer has both integrated and discrete video options. |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video type: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | integrated on system board, 128-bit hardware accelerated |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Data bus | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | integrated video |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video controller | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Intel Extreme Graphics |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video memory | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Integrated video up to 128 MB of shared system memory. <span style="color:#000080;">'''NOTE:&nbsp;'''</span>Up to 128 MB shared if total computer memory is 512 MB or greater; up to 64 MB shared if total computer memory is less than 512 MB. |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | LCD interface | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | LVDS |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | TV support | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | NTSC or PAL in S-video and composite modes |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Color output | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 16.7 million |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video type: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | discrete video adapter, 128-bit hardware accelerated |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Data bus | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | PCI-E x16 |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video controller | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | ATI Mobility Radeon X300 |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Video memory | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 64 MB |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | LCD interface | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | LVDS |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | TV support | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | NTSC or PAL in S-video and composite modes |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Color output | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 16.7 million |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Audio''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Audio type | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | AC'97 (Soft Audio) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Audio controller | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Sigmatel 9751 |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Stereo conversion | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 18-bit (analog-to-digital) 20-bit (digital-to-analog) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Interfaces: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Internal | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | AC'97 |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | External | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | microphone-in connector, stereo headphones/speakers connector |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Speaker | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | two 4-ohm speakers |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Internal speaker amplifier | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 2-W channel into 4 ohms |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Volume controls | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | keyboard shortcuts, program menus, mute and volume-up/down buttons |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Display''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Type (active-matrix TFT) | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | XGA; SXGA+ |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Dimensions: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Height | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 214.3 mm (8.4 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 285.7 mm (11.3 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Diagonal | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 357.1 mm (14.1 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Maximum resolutions: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | XGA | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 1024 x 768 at 262,000 colors |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | SXGA+ | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 1400 x 1050 at 262,000 colors |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating angle | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0º&nbsp;(closed) to 180° |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Viewing angles: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Horizontal | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | ±40° |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Vertical | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | +10°/–30° |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Pixel pitch: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | XGA | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0.28 mm (12.1 inch); 0.297 mm (14.1 inch) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | SXGA+ | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0.204 mm (14.1 inch) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Power consumption (panel with backlight) (maximum): | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | XGA | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 6.0 W |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | SXGA+ | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 6.5 W |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Controls | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | brightness can be controlled through keyboard shortcuts |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Keyboard''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Number of keys | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 87 (U.S. and Canada); 88 (Europe); 91 (Japan) |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Layout | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | QWERTY/AZERTY/Kanji |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Touch Pad''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | X/Y position resolution (graphics&nbsp;table mode) | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 240 cpi |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Size: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 64.88 mm (2.55-inch) sensor-active area |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Height | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 48.88-mm (1.92-inch) rectangle |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Track Stick''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | X/Y position resolution (graphics&nbsp;table mode) | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 250 count/sec @ 100 gf |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Size | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | protrudes 0.5 mm higher than surrounding keycaps |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Battery''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Type | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 6-cell "smart" lithium ion (53 WHr) (standard)4-cell "smart" lithium ion (32 WHr) (optional) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Dimensions: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Depth | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 88.5 mm (3.48 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Height | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 21.5 mm (0.83 inch) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 139.0 mm (5.47 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Weight | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0.32&nbsp;kg&nbsp;(0.70&nbsp;lb)&nbsp;(6&nbsp;cell) 0.25&nbsp;kg&nbsp;(0.56&nbsp;lb)&nbsp;(4&nbsp;cell) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Voltage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 14.8 VDC |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Charge time (approximate): | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Computer on | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 2.5 hours |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Computer off | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 1 hour |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating time | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | varies depending on operating conditions and can be significantly reduced under certain power-intensive conditions See&nbsp;[http://www.solano.edu/technology100218/data/D610/battery.htm#wp1054784 Using a Battery]&nbsp;for more information on battery life and operating time. |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Life span (approximate) | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 300 discharge/charge cycles |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Temperature range: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0°&nbsp;to&nbsp;35°C&nbsp;(32°&nbsp;to&nbsp;95°F) |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | –20°&nbsp;to 65°C (–4° to 149°F) |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''AC Adapter''' |- style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | <span style="color:#000080;">'''NOTE:&nbsp;'''</span>The 90-W AC adapter is optional and may not ship with your computer. |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Types | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 90 W and 65 W |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Input voltage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 90–264 VAC (both) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Input current (maximum) | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 1.7 A (both) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Input frequency | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 47–63 Hz (both) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Output current: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 90 W | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 5.62 A (maximum at 4-second pulse); 4.62 A (continuous) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 65 W | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 4.34 A (maximum at 4-second pulse); 3.34 A (continuous) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Output power | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 90 W or 65 W |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Rated output voltage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 19.5 VDC (both) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Dimensions: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Height | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 33.8–34.6 mm (1.34–1.36 inches) (90 W) 27.8–28.6 mm (1.10–1.12 inches) (65 W) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 60.9 mm (2.39 inches) (90 W) 57.9 mm (2.28 inches) (65 W) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Length | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 153.42 mm (6.04 inches) (90 W) 137.2 mm (5.40 inches) (65 W) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Weight (without cables) | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0.46 kg (1.01 lb) (90 W) 0.36 kg (0.79 lb) (65 W) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Temperature range: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0° to 35°C (32° to 95°F) (both) |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | –40° to 65°C (–40° to 149°F) (both) |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Physical''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Height | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 34.3 mm (1.4 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Width | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 312.0 mm (12.5 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Depth | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 262.2 mm (10.5 inches) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Weight: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | With travel module | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 2.2 kg (4.85 lb) (6 cell) 2.1 kg (4.68 lb) (4 cell) |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | With CD drive | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 2.4 kg (5.29 lb) (6 cell) |- |} <div style="margin-left:0cm;margin-right:0cm;"></div> {| style="border-spacing:0;width:11.899cm;" |- style="border-top:0.5pt solid #808080;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | colspan="2" | '''Environmental''' |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Temperature range: | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0°&nbsp;to 35°C (32° to 95°F) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | –40°&nbsp;to 65°C (–40° to 149°F) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Relative humidity (maximum): | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 10% to 90% (noncondensing) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 5% to 95% (noncondensing) |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Maximum vibration (using a random-vibration spectrum that simulates user environment): | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 0.66 GRMS |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 1.30 GRMS |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Maximum shock (measured with hard drive in head-parked position and a 2-ms half-sine pulse): | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 142 G, 70 in/s |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | 163 G |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Altitude (maximum): | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | &nbsp; |- | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Operating | style="border-top:none;border-bottom:0.05pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | –15.2 to 3048 m (–50 to 10,000 ft) |- | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.5pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | Storage | style="border-top:none;border-bottom:0.5pt solid #808080;border-left:0.05pt solid #808080;border-right:0.5pt solid #808080;padding:0.071cm;" | –15.2 to 10,668 m (–50 to 35,000 ft) |- |} 131b2da333c1732623d1171516e665b934521d52 0 599 2650 2649 2022-04-09T12:42:59Z Pvdm 2 wikitext text/x-wiki /usr/bin/chromium -high-dpi-support=1 -force-device-scale-factor=1 --enable-features=UseOzonePlatform --ozone-platform=wayland %U /usr/bin/google-chrome-stable -high-dpi-support=1 -force-device-scale-factor=1 --enable-features=UseOzonePlatform --ozone-platform=wayland %U 56206d10304b12989e8f75a982311423485b6fb3 0 554 2659 2298 2022-06-22T16:39:14Z Pvdm 2 wikitext text/x-wiki Show configs: # snapper list-configs Create snapshot: # snapper -c home create --description "/home snapshot" View snapshots: # snapper -c home ls =delete snapper config= # snapper -c home delete-config If that does not work: * remove /home from fstab * reboot and log in as root * <pre>cd {vol}/.snapshots (b.v. /home/.snapshots)</pre> * <pre># for i in $(ls -1); do btrfs property set -ts $i/snapshot/ ro false; done</pre> * <pre># rm -rf *</pre> * <pre># ..</pre> * <pre># rmdir .snapshots</pre> 681f3bf42db3bd5a4da6b3d638c16639a10d7723 0 601 2661 2022-07-14T06:27:42Z Pvdm 2 Created page with "<pre> Then start GParted or another disk management app, delete the swap partition, expand your partitions (BTRFS can be grown online, no need for reboot). Create a subvolume to store your swap. Then create a swap file: https://wiki.archlinux.org/title/Swap#Swap_file You may wish to disable Copy On Write on your swap file.</pre>" wikitext text/x-wiki <pre> Then start GParted or another disk management app, delete the swap partition, expand your partitions (BTRFS can be grown online, no need for reboot). Create a subvolume to store your swap. Then create a swap file: https://wiki.archlinux.org/title/Swap#Swap_file You may wish to disable Copy On Write on your swap file.</pre> 70cad8cca792d770f977531960f2c4775640dca8 0 396 2664 2663 2022-09-17T09:15:11Z Pvdm 2 wikitext text/x-wiki *[[hardware]] *[[disks]] *[[lsmod]] *[[lspci]] Per 20220917: 10:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1) ae1cff7ff7d78cff334302d1fe8e629eb64b8581 0 597 2666 2651 2022-09-17T12:00:25Z Pvdm 2 wikitext text/x-wiki HP Envy x360 Convertible Model 15-ed0300nd ProdID 3K787EA#ABH --- {| style="border-spacing:0;width:37cm;" |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Productnummer'''</span> | style="color:#000000;" | 3K787EA |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Productnaam'''</span> | style="color:#000000;" | HP ENVY x360 Laptop - 15-ed0300nd |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Microprocessor'''</span> | style="color:#000000;" | Intel® Core™ i7-10510U (1,8 GHz basisfrequentie, tot 4,9 GHz basisfrequentie met Intel® Turbo Boost-technologie, 8 MB cache, 4 cores) |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Chipset'''</span> | style="color:#000000;" | Intel® geïntegreerde SoC |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Geheugen, standaard'''</span> | style="color:#000000;" | 16 GB DDR4-2666 SDRAM (2 x 8 GB) |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Videographics'''</span> | style="color:#000000;" | NVIDIA® GeForce® MX330 (4 GB GDDR5 gereserveerd) |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Vaste schijf'''</span> | style="color:#000000;" | 1 TB PCIe® NVMe™ M.2 SSD |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Optische drive'''</span> | style="color:#000000;" | Optische drive niet inbegrepen |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Beeldscherm'''</span> | style="color:#000000;" | 39,6 cm (15,6 inch) wled-backlit FHD IPS met smalle randen, glas van rand tot rand en multitouch-ondersteuning, 250 nits, 45% NTSC (1920 x 1080) |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Draadloze verbinding'''</span> | style="color:#000000;" | Intel® Wi-Fi 6 AX 201 (2x2) en Bluetooth® 5 combo (ondersteuning voor Gigabit-overdrachtssnelheden) |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Uitbreidingssleuven'''</span> | style="color:#000000;" | 1 multi-formaat SD-mediakaartlezer |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Externe poorten'''</span> | style="color:#000000;" | 1 SuperSpeed USB Type-C® 10Gbps signaling rate (USB Power Delivery, DisplayPort™ 1.2, HP Sleep and Charge); 1 SuperSpeed USB Type-A 5Gbps signaling rate (HP Sleep and Charge); 1 SuperSpeed USB Type-A 5Gbps signaling rate; 1 HDMI 2.0; 1 AC smart pin; 1 headphone/microphone combo |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Minimumafmetingen (b x d x h)'''</span> | style="color:#000000;" | 35,8 x 23 x 1,89 cm |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Gewicht'''</span> | style="color:#000000;" | 1,97 kg |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Voedingstype'''</span> | style="color:#000000;" | 65-Watt netvoedingsadapter |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Batterijtype'''</span> | style="color:#000000;" | 3-cels, 51-WHr lithium-ion |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Accuwerktijd bij gemengd gebruik'''</span> | style="color:#000000;" | Tot 8 uur en 30 minuten |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Accuwerktijd bij afspelen van video's'''</span> | style="color:#000000;" | Tot 10 uur en 45 minuten |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Webcam'''</span> | style="color:#000000;" | HP Wide Vision HD-camera met cameraklepje en ingebouwde digitale dual array-microfoon |- style="border:0.05pt solid #cccccc;padding:0.265cm;" || <span style="color:#000000;">'''Audiokenmerken'''</span> | style="color:#000000;" | Audio van Bang & Olufsen; 3 speakers; HP Audio Boost 2.0 |- |} <pre> Envy:~ # inxi -F System: Host: Envy Kernel: 5.19.8-1-default arch: x86_64 bits: 64 Console: pty pts/1 Distro: openSUSE Tumbleweed 20220914 Machine: Type: Convertible System: HP product: HP ENVY x360 Convertible 15-ed0xxx v: Type1ProductConfigId serial: CND02035YM Mobo: HP model: 8757 v: 08.32 serial: PJUJAC21TDPB4P UEFI: Insyde v: F.11 date: 06/08/2020 Battery: ID-1: BAT1 charge: 40.2 Wh (100.0%) condition: 40.2/51.0 Wh (78.9%) CPU: Info: quad core model: Intel Core i7-10510U bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 2300 min/max: 400/4900 cores: 1: 2300 2: 2300 3: 2300 4: 2300 5: 2300 6: 2300 7: 2300 8: 2300 Graphics: Device-1: Intel CometLake-U GT2 [UHD Graphics] driver: i915 v: kernel Device-2: NVIDIA GP108M [GeForce MX330] driver: N/A Device-3: Chicony HP Wide Vision HD Camera type: USB driver: uvcvideo Display: server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 driver: X: loaded: modesetting,nvidia gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 22.1.7 Audio: Device-1: Intel Comet Lake PCH-LP cAVS driver: sof-audio-pci-intel-cnl Sound Server-1: ALSA v: k5.19.8-1-default running: yes Sound Server-2: PulseAudio v: 16.1 running: yes Sound Server-3: PipeWire v: 0.3.57 running: yes Network: Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi IF: wlo1 state: up mac: 3c:58:c2:7c:f3:d5 Bluetooth: Device-1: Intel AX201 Bluetooth type: USB driver: btusb Report: rfkill ID: hci0 state: up address: see --recommends RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci Drives: Local Storage: total: 953.87 GiB used: 570.99 GiB (59.9%) ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW010T8H size: 953.87 GiB Partition: ID-1: / size: 100 GiB used: 38.44 GiB (38.4%) fs: btrfs dev: /dev/nvme0n1p5 ID-2: /boot/efi size: 256 MiB used: 81 MiB (31.7%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 100 GiB used: 61.38 GiB (61.4%) fs: btrfs dev: /dev/nvme0n1p6 ID-4: /opt size: 100 GiB used: 38.44 GiB (38.4%) fs: btrfs dev: /dev/nvme0n1p5 ID-5: /var size: 100 GiB used: 38.44 GiB (38.4%) fs: btrfs dev: /dev/nvme0n1p5 Swap: ID-1: swap-1 type: partition size: 15.37 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p8 Sensors: System Temperatures: cpu: 38.0 C pch: 35.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 359 Uptime: 0h 58m Memory: 15.37 GiB used: 2.67 GiB (17.4%) Shell: Bash inxi: 3.3.21 0d42486a418d18638656f9d9dc5de42eb0d9d37d 0 602 2669 2668 2022-10-10T09:56:21Z Pvdm 2 wikitext text/x-wiki * 7 iNch standaard display, 1024 × 600 Hardware resolutie, tot 1920x1080 Software configuratie resolutie. ●.Capacitieve touchscreen, maximale ondersteuning 5 punt touch. ●.Ondersteuning backlight controle alleen, de achtergrondverlichting kan worden uitgeschakeld om stroom te besparen. ●. Ondersteuning Raspberry Pi, BB Zwart, Banana Pi en andere mainstream mini PC. ●.Kan worden gebruikt als algemene doeleinden gebruiken HDMI monitor, bijvoorbeeld: verbinden met een computer HDMI als de sub-display. ●.Gebruikt als een raspberry pi display dat ondersteunt Raspbian, Ubuntu, Kali-Linux, Kodi, win10 IOT, single-touch, gratis drive. ●.Werken als een PC monitor, ondersteuning win7, win8, win10 systeem 5 punt touch (XP en oudere versie systeem: single-point touch), Gratis drive. ●.CE, RoHS certificering <pre> Na de programmering van Step1 is voltooid, open de config.txt bestand van TF card root directory en Voeg de volgende code op het einde van het bestand, opslaan en eject Micro Sd-kaart veilig: max_usb_current = 1 Hdmi_force_hotplug = 1 Config_hdmi_boost = 7 Hdmi_group = 2 Hdmi_mode = 87 Hdmi_drive = 1 Display_rotate = 0 Hdmi_cvt 1024 600 60 6 0 0 0 447708d3d508842b528def76c179353491db1707 6 604 2683 2022-12-08T19:40:35Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 455 2701 2652 2022-12-26T08:59:13Z Pvdm 2 /* Envy */ wikitext text/x-wiki =General tips= The ultimate solution to ugly fonts is to use more pixels to draw them. That translates to using a larger nominal pixel size. when that has the effect of making fonts too big, more screen resolution is required at the same physical size. More pixels has a cubic effect, meaning it doesn’t require much more in nominal size to have a big effect. Sometimes in order to make all screen objects bigger, people use a lower screen resolution than the optimal one a screen supports. This has the opposite effect, making fonts spindly or otherwise ugly. IOW, if your screen supports 1920x1080 but you are using 1366x768, a switch to using 1920x1080 and an increase nominal font sizes in settings is required. I keep screen DPI set to 120 on a 24" 1920x1200 screen. The combination of 24" and 1920x1200 calculates to a DPI of 94. The application of a logical DPI of 120 results in fonts big enough to see that are never ugly. A 12pt font @120 DPI uses ~200px per glyph, compared to ~128 used @96 DPI, >56% more at the same physical size. The screen can’t actually produce that much resolution, but the effect of trying by the X server, with or without subpixel, hinting or anti-aliasing, works like magic. =Envy= <pre> pvdm@Envy:~> xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.00*+ 40.00 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) </pre> DPI=140,093023256 of 142 =lesie= <pre> sietske@lesie:~> xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.03*+ 60.01 59.97 59.96 59.93 DISPLAY: 15.6”, Full HD (1920 x 1080), IPS Diagonal 15.6" Pixel density 141.21 ppi Panel Type IPS Resolution 1920 x 1080 Becomes "Retina" from 24 inches (62 cm) </pre> =HP elitebook 8570p= <pre> Horizontal pixels: 1600 Vertical pixels: 900 Diagonal size (inches): 15,77 Pixels per Inch PPI: 116.41 Dot Pitch: 0.22 Screen Width: 13.74 Screen Height: 7.73 pvdm@lapx:~> xrandr Screen 0: minimum 320 x 200, current 1600 x 900, maximum 16384 x 16384 LVDS connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1600x900 60.0*+ 40.0 1440x900 59.9 1280x854 59.9 1280x800 59.8 1280x720 59.9 1152x768 59.8 1024x768 59.9 800x600 59.9 848x480 59.7 720x480 59.7 640x480 59.4 </pre> =samsung rv720 bla= <pre> samsie:~ # xrandr Screen 0: minimum 320 x 200, current 1600 x 900, maximum 16384 x 16384 LVDS connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1600x900 60.03*+ 40.02 1440x900 59.89 1280x854 59.89 1280x800 59.81 1280x720 59.86 1152x768 59.78 1024x768 59.92 800x600 59.86 848x480 59.66 720x480 59.71 640x480 59.38 </pre> 116 DPI PvdM =tabel= {| style="border-spacing:0;" | style="background-color:#9999ff;border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| resolutie | style="background-color:#9999ff;border:0.05pt solid #000000;padding:0.97mm;"| Dichtheid |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 7” 15:9 15,3x9,15 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 800x480 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 133 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 8,9” 16:9 19,55x11,45 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1024x600 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 133 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 10,2” 16:9 22,3x13,05 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1024x600 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 117 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 10,6” 15:9 23,1x13,8 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1280x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 141 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 11,1” 16:9 24,9x13,8 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1366x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 141 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 12” 4:3 24,7x18,5 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1024x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 105 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1400x1050 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 144 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 12,1” 16:10 26,1x16,3 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1280x800 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 125 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1440x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 140 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 13” 16:9 29x16,35 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1366x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 120 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1600x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 140 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 13.1” 16:10 28,5x17,9 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1280x800 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 114 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1440x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 128 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 14” 4:3 28,5x21,4 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1024x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 91 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1400x1050 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 125 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 14,1” 16:10 30,4x19 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1280x800 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 107 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1440x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 120 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 15” 4:3 30,4x22,8 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1024x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 86 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1400x1050 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 117 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1600x1200 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 134 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 15,4” 16:10 33,15x20,82 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1280x800 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 98 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1440x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 110 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1680x1050 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 129 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1920x1200 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 147 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 16” 16:9 35,3x19,9 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1366x768 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 98 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1920x1080 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 138 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 16,4” 16:9 36,3x20,4 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1600x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 112 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1920x1080 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 134 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 17,1” 16:10 36,8x23 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1440x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 98 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1680x1050 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 116 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1920x1200 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 133 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 18,4” 16:9 40,9x23 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1680x945 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 104 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1920x1080 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 119 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 19” 16:10 41x25,6 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1440x900 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 89 |- | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 20” 16:10 43,4x27,1 | style="background-color:#99cc99;border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| 1680x1050 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| 98 |- | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.97mm;"| | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:0.05pt solid #000000;padding:0.97mm;"| |} 9bb3c48697fadc5e4e09715e2a6e209981ac3653 0 605 2705 2704 2023-01-16T06:54:57Z Pvdm 2 wikitext text/x-wiki # cpupower frequency-set -g performance or <pre> #!/bin/sh # # puts cpus in performance mode # echo "performance" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor de92fdc4f741c9b9b343ab4a75840db6b159bb01 0 472 2706 1805 2023-01-16T09:50:10Z Pvdm 2 wikitext text/x-wiki =Old German 320 nWb/m level= Reference fluxivity of G320 nWb/m is consistent with the German flux measurements made in the 1950’s that are used in the UK and Europe to this day. The actual fluxivity of these recordings as measured by DIN 45520 or AES7/ANSI S4.6 is '''290nWb/m'''. The original tape flux measurements were made in Germany in the late 1950’s, using a transfer-to-dc method standardized in German Standard DIN 45520. These measurements are the basis for the reference fluxivity of 320 nWb/m used on German calibration tapes made by BASF and Agfa (now a part of BASF). In the late 1960’s Ampex used the ANSI method to measure the German tapes, and found that the German reference fluxivity was not 320 nWb/m, but only 290 nWb/m, which is about 1 dB low. Recent new measurements at MRL have confirmed that flux measurement by the transfer-to-dc method used in Germany gives exactly the same results as the ANSI method. So MRL have concluded that the original (1950’s) German measurement was in error by 10%. The MRL Calibration Tapes made to conform to the old German measurements were previously identified by MRL as “320” nWb/m; this has now been changed to G320 nWb/m, indicating 320 nWb/m according to the original German measurement. <pre> Operating Level Flux@1000Hz Flux@700Hz 0dB 180 nWb/m 185 nWb/m +1dB 200 nWb/m +2dB 224 nWb/m +3dB 250 nWb/m 260 nWb/m +4dB 280 nWb/m G320 nWb/m +5dB 315 nWb/m +6dB 355 nWb/m 370 nWb/m +7dB 400 nWb/m +8dB 450 nWb/m G510 nWb/m +9dB 500 nWb/m Magnetic Flux level flux Φ LΦ 520 nWb/m +6.36 dB 370 nWb/m +3.41 dB 320 nWb/m +2.14 dB 250 nWb/m 0 dB 220 nWb/m −1.11 dB 200 nWb/m −1.94 dB 185 nWb/m −2.62 dB 150 nWb/m −4.44 dB </pre> 1/4 track machines will respond different that 1/2 track machines. The 1/2 track decks can use 370 nWb/M (+6dB) but the A2300 will not work well with that level. It needs to be no higher than 250 but more correct 200 if you want full bandwidth. Like a lot of guys are oing they get blinded except for one spec and that is flux density. This may enhance S/N ratio but also distortion goes up and bandwidth goes down. So you are better off with a 200nWb/M tape for the A2300 at 7.5 IPS and can also be used on the quad Otari. The 25-2 is not going to like the levels above 250 nWb/M as it is designed and the A7300-2T is better off at 250 as well. If you want to run 370 nWb/M the Tascam 52, 62 and ATR units are more suited and have jumpers for those levels. Higher is not always better! The track width of machines has a lot to do with how much flux you can throw at it. The 1/4 track decks like to have 200nWb/M and on a rare occasion maybe 250 but nothing higher. the 1/2 track machines is where you have many options and depending on the speed you might be able to throw a lot of signal at it. You know the other thing in upping the flux density- the tape has a fixed saturation point let just say +15. If you go and set up a deck for +6(370) instead or +3 (250) then what you risk is a saturation happening sooner as you then do not have +15 headroom but +9. 861505eb00d921ddc67b9447eef310a0c9b9eb01 0 606 2714 2023-01-19T11:52:46Z Pvdm 2 Created page with "qpwgraph pw-top pw-cat - Play and record media with PipeWire pw-dump pw-dsdplay pw-play pw-record" wikitext text/x-wiki qpwgraph pw-top pw-cat - Play and record media with PipeWire pw-dump pw-dsdplay pw-play pw-record 783b4c670582d1553b095dca5009bebfa0b6624a 0 603 2724 2723 2023-05-02T17:55:22Z Pvdm 2 /* play */ wikitext text/x-wiki =generate file= Generate 1 second of white noise. sox -n output.wav synth 1 noise Generate a 1-second sine tone. sox -n output.wav synth 1 sine 440 Generate a 10-second sine sweep file. sox -n output.wav synth 10 sine 0:20000 Exponential sine sweep sox -n -r 44100 sine-sweep.wav synth 10 sine 5/22050 =play= Play synthesized audio. play -n synth sine 440 trim 0 1 gain -12 Play sine verbose 24 bits /=exponential play -V -n -b 24 -r 48000 synth 10 sine 20/20000 play -V -n -b 24 -r 48000 synth 10 sine 20/20000 vol -50dB And then ARTA: <pre> Fs (Hz): 192000 FFT: 4096 Wnd: FlatTop Avg: Peak Hold </pre> =calibration tones= Play 30 tones at once, for frequency adjustment of equipment etc. play -r 192000 -V -n synth 300 sin 20 sin 25 sin 31.5 sin 40 sin 50 sin 63 sin 80 sin 100 sin 125 sin 160 sin 200 sin 250 sin 315 sin 400 sin 500 sin 630 sin 800 sin 1000 sin 1250 sin 1600 sin 2000 sin 2500 sin 3150 sin 4000 sin 5000 sin 6300 sin 8000 sin 10000 sin 12500 sin 16000 sin 20000 remix 1-31 1-31 where: 192000 is the samplerate, if your card supports it 300 is number of seconds - This results in the following spectrum: [[File:30-tone-spectrum.png|left]] If you want to generate the file yourself, use: sox -r 192000 -V -n "31 frequencies.flac" synth 300 sin 20 sin 25 sin 31.5 sin 40 sin 50 sin 63 sin 80 sin 100 sin 125 sin 160 sin 200 sin 250 sin 315 sin 400 sin 500 sin 630 sin 800 sin 1000 sin 1250 sin 1600 sin 2000 sin 2500 sin 3150 sin 4000 sin 5000 sin 6300 sin 8000 sine 10000 sin 12500 sin 16000 sin 20000 remix 1-31 1-31 <br> It will create a 300-seconds FLAC file with the 31 tones called "31 frequencies.flac" <br> <br> <br> =modify= Reduce level by 12dB sox speech.wav output.wav gain -12 Crop to the first 1 second of the file. sox speech.wav output.wav trim 0 1 Reverse the contents. sox speech.wav output.wav reverse Normalise the contents to 0dBFS. sox speech.wav output.wav norm Equaliser (-6dB @ 100Hz, -24dB @ 8000Hz) sox speech.wav output.wav bass -6 100 treble -24 8000 Add room modelling reverb. sox speech.wav output.wav reverb 50 50 100 Trim digital silence from start and end. sox input.wav trimmed/output.wav silence 1 0.1 0 1 0.1 0 - sox infile outfile gain -n normalises to 0dB, and sox infile outfile gain -n -3 normalises to -3dB. =effects= chorus effect: A typical delay is around 40ms to 60ms; the modulation speed is best near 0.25Hz and the modulation depth around 2ms. For example, a single delay: play guitar1.wav chorus 0.7 0.9 55 0.4 0.25 2 -t Two delays of the original samples: play guitar1.wav chorus 0.6 0.9 50 0.4 0.25 2 -t 60 0.32 0.4 1.3 -s A fuller sounding chorus (with three additional delays): play guitar1.wav chorus 0.5 0.9 50 0.4 0.25 2 -t 60 0.32 0.4 2.3 -t 40 0.3 0.3 1.3 -s =compand= The following example might be used to make a piece of music with both quiet and loud passages suitable for listening to in a noisy environment such as a moving vehicle: sox asz.wav asz-car.wav compand 0.3,1 6:-70,-60,-20 -5 -90 0.2 The transfer function (`6:-70,...') says that very soft sounds (below -70dB) will remain unchanged. This will stop the compander from boosting the volume on `silent' passages such as between movements. However, sounds in the range -60dB to 0dB (maximum volume) will be boosted so that the 60dB dynamic range of the original music will be compressed 3-to-1 into a 20dB range, which is wide enough to enjoy the music but narrow enough to get around the road noise. The `6:' selects 6dB soft-knee compand-ing. The -5 (dB) output gain is needed to avoid clipping (the number is inexact, and was derived by experimentation). The -90 (dB) for the initial volume will work fine for a clip that starts with near silence, and the delay of 0.2 (seconds) has the effect of causing the compander to react a bit more quickly to sudden volume changes. =general= --multi-threaded | --single-threaded By default, SoX is `single threaded'. If the --multi-threaded option is given however then SoX will process audio channels for most multi-channel effects in parallel on hyper-threading/multi- core architectures. This may reduce processing time, though sometimes it may be necessary to use this option in conjuction with a larger buffer size than is the default to gain any benefit from multi-threaded processing (e.g. 131072; see --buffer above). 5969fada2756a1414919d164b3c870e91b14d26e 0 607 2726 2023-05-04T11:07:20Z Pvdm 2 Created page with " $ pkexec env "DISPLAY=$DISPLAY" "XAUTHORITY=$XAUTHORITY" "QT_QPA_PLATFORMTHEME=kde" systemsettings then change theme as normal." wikitext text/x-wiki $ pkexec env "DISPLAY=$DISPLAY" "XAUTHORITY=$XAUTHORITY" "QT_QPA_PLATFORMTHEME=kde" systemsettings then change theme as normal. fdd53523fc6a0201f812931790c3921cd58aedcb 0 574 2727 2463 2023-06-20T16:45:30Z Pvdm 2 /* De volgende stappen zijn nodig: */ wikitext text/x-wiki =RAID vergroten= Ter referentie, hier enkele veel gebruikte commando's: <pre> # cat /proc/mdstat: geef status, ook rebuild voortgang # mdadm -D /dev/md[012]: detail over RAID # mdadm - -stop /dev/md2, eerst umount /dev/md2: om een RAID te stoppen # mdadm - -assemble - -scan: assemble all raids # mdadm - -assemble /dev/md1 /dev/sda2 /dev/sdb2 /dev/sdc2: assemblatie # mdadm -f /dev/sda1: fail deze partitie (mark as FAULTY) # mdadm -r /dev/sda1: remove deze partitie # mdadm - -re-add /dev/md1 /dev/sdb2 *(veel gebruikt): om een recently removede schijf weer toe te voegen doe dit nadat de schijf er weer is. # mdadm -a /dev/mdx: hot add listed devices # mdadm - -stop /dev/md2: stop de array # Mdadm -A - -scan: start the arrays </pre> =De volgende stappen zijn nodig:= 0. zet de automatische reboot van de server UIT! 1. Selekteer een disk en verwijder hem van de array. Voer de 2 commando’s achter elkaar uit: # mdadm -f /dev/md1 /dev/sdd1 - fail device # mdadm -r /dev/md1 /dev/sdd1 - remove device Het laatste commando doet het niet als drive al weg is, dus doe het voor loskoppelen. Daarna de oude drive loshalen en sluit de nieuwe drive aan. 2. partitioneer de nieuwe drive naar de volledige grootte. Laat op linux FS staan, dit werkt ook – PvdM 2017 # fdisk /dev/sdd g: create new GPT partition table n: new partition en 4x enter w: write and quit: 3. Voeg de nieuwe disk aan het array toe: # mdadm --add /dev/md1 /dev/sde1 - add device, start immediate rebuild 4. Daarna kun je het hele proces in de gaten houden met: # watch cat /proc/mdstat # mdadm –detail /dev/md1 5. Wacht tot de resync klaar is. Hierna moet de stappen 1-4 herhalen voor elke schijf. 6. Hierna kun je de ruimte op het array vergroten: # mdadm --grow /dev/md0 --size=max - change the size of an active array Dit duurt even, de extra (lege haha) ruimte wordt nu gesyncd. 7. Het array bevat nu 1 disk met alle beschikbare ruimte. 8. Nu de onderliggende partitie is vergroot, moet je je filesystem resizen. Maar eerst wil je een filesystemcheck uitvoeren. Dit kan niet als het gemount is. # umount [mountpoint] # fsck /dev/md1 9. For an ext2/ext3/ext4 filesystem: # resize2fs /dev/md1 =Na het wegvallen van 1 harddisk= # mdadm /dev/md1 --add /dev/sdX en dan werkt het weer eeb223faf2414eb02224fefc5c0b3dafb0889cef 0 557 2728 2582 2023-06-23T18:51:24Z Pvdm 2 wikitext text/x-wiki snaar/belt: 63 mm OR 67mm x 0.6 OR 0,8mm drdcc: We have tried all sizes. I believe that the 0.7 is the better option. Ralf c8a793a951f03ad6f294017a69ff1f2c212397a6 0 482 2734 2733 2023-08-30T14:18:30Z Pvdm 2 wikitext text/x-wiki * Boot from live dvd OR choose RESCUE from boot USB (graphical desktop is ok) * use gparted to find boot partition * mount /dev/sdX /mnt mount /dev/sda5 /mnt * mount –-bind /dev /mnt/dev * mount –-bind /proc /mnt/proc * mount –-bind /sys /mnt/sys * chroot /mnt * grub2-mkconfig -o /boot/grub2/grub.cfg * grub2-install /dev/sda * chtrl-d 'exit' * reboot =grub edit= F2 into grub CLI insmod ntldr insmod ntfs insmod chain set root=(hd0,msdos1) chainloader +1 boot d9e9f4da1106c2fb4c3df0507c3485b9118a3a74 0 504 2735 2729 2023-09-01T20:09:25Z Pvdm 2 /* envy - tumbleweed */ wikitext text/x-wiki __FORCETOC__ = envy - tumbleweed= <pre> 230901 pvdm@Envy:~> glmark2 ======================================================= glmark2 2021.12 ======================================================= OpenGL Information GL_VENDOR: NVIDIA Corporation GL_RENDERER: NVIDIA GeForce MX330/PCIe/SSE2 GL_VERSION: 4.6.0 NVIDIA 535.86.05 Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0 Surface Size: 800x600 windowed ======================================================= ======================================================= glmark2 Score: 5096 ======================================================= 230625 # prime-run konsole # glmark2-wayland ======================================================= glmark2 2021.12 ======================================================= OpenGL Information GL_VENDOR: Intel GL_RENDERER: Mesa Intel(R) UHD Graphics (CML GT2) GL_VERSION: 4.6 (Compatibility Profile) Mesa 23.1.3 Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0 Surface Size: 800x600 windowed ======================================================= [build] use-vbo=false: FPS: 10414 FrameTime: 0.096 ms [build] use-vbo=true: FPS: 10491 FrameTime: 0.095 ms [texture] texture-filter=nearest: FPS: 10216 FrameTime: 0.098 ms [texture] texture-filter=linear: FPS: 10029 FrameTime: 0.100 ms [texture] texture-filter=mipmap: FPS: 10562 FrameTime: 0.095 ms [shading] shading=gouraud: FPS: 8441 FrameTime: 0.118 ms [shading] shading=blinn-phong-inf: FPS: 8086 FrameTime: 0.124 ms [shading] shading=phong: FPS: 7001 FrameTime: 0.143 ms [shading] shading=cel: FPS: 6635 FrameTime: 0.151 ms [bump] bump-render=high-poly: FPS: 4716 FrameTime: 0.212 ms [bump] bump-render=normals: FPS: 10871 FrameTime: 0.092 ms [bump] bump-render=height: FPS: 9692 FrameTime: 0.103 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 4881 FrameTime: 0.205 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 1661 FrameTime: 0.602 ms [pulsar] light=false:quads=5:texture=false: FPS: 8999 FrameTime: 0.111 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 1833 FrameTime: 0.546 ms [desktop] effect=shadow:windows=4: FPS: 5159 FrameTime: 0.194 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 808 FrameTime: 1.239 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 1344 FrameTime: 0.744 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 975 FrameTime: 1.026 ms [ideas] speed=duration: FPS: 6467 FrameTime: 0.155 ms [jellyfish] <default>: FPS: 4973 FrameTime: 0.201 ms [terrain] <default>: FPS: 310 FrameTime: 3.236 ms [shadow] <default>: FPS: 5495 FrameTime: 0.182 ms [refract] <default>: FPS: 669 FrameTime: 1.495 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 7606 FrameTime: 0.131 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 7685 FrameTime: 0.130 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 7589 FrameTime: 0.132 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 7639 FrameTime: 0.131 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 7812 FrameTime: 0.128 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 7628 FrameTime: 0.131 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 7625 FrameTime: 0.131 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 7756 FrameTime: 0.129 ms ======================================================= glmark2 Score: 6425 ======================================================= <pre>220817 ======================================================= glmark2 2021.12 ======================================================= OpenGL Information GL_VENDOR: NVIDIA Corporation GL_RENDERER: NVIDIA GeForce MX330/PCIe/SSE2 GL_VERSION: 4.6.0 NVIDIA 515.65.01 Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 Surface Size: 800x600 windowed ======================================================= glmark2 Score: 4729 ======================================================= 220525 pvdm@Envy:~> glmark2 ======================================================= glmark2 2021.12 ======================================================= OpenGL Information GL_VENDOR: NVIDIA Corporation GL_RENDERER: NVIDIA GeForce MX330/PCIe/SSE2 GL_VERSION: 4.6.0 NVIDIA 515.43.04 Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 Surface Size: 800x600 windowed ======================================================= glmark2 Score: 4617 ======================================================= 20220514 pvdm@Envy:~> glmark2 ======================================================= glmark2 2021.12 ======================================================= OpenGL Information GL_VENDOR: Intel GL_RENDERER: Mesa Intel(R) UHD Graphics (CML GT2) GL_VERSION: 4.6 (Compatibility Profile) Mesa 22.0.3 Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 Surface Size: 800x600 windowed ======================================================= glmark2 Score: 3100 ======================================================= 20220514 pvdm@Envy:~> glmark2-wayland ======================================================= glmark2 2021.12 ======================================================= OpenGL Information GL_VENDOR: Intel GL_RENDERER: Mesa Intel(R) UHD Graphics (CML GT2) GL_VERSION: 4.6 (Compatibility Profile) Mesa 22.0.3 Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 Surface Size: 800x600 windowed ======================================================= glmark2 Score: 4053 ======================================================= pvdm@Envy:~> glmark2 ======================================================= glmark2 2020.04 ======================================================= OpenGL Information GL_VENDOR: Intel Open Source Technology Center GL_RENDERER: Mesa DRI Intel(R) UHD Graphics (CML GT2) GL_VERSION: 3.0 Mesa 20.3.3 ======================================================= glmark2 Score: 2866 ======================================================= pvdm@Envy:~> </pre> =lapx - tumbleweed = <pre><nowiki>pvdm@tumbleweed:~> glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: X.Org GL_RENDERER: Gallium 0.4 on AMD TURKS (DRM 2.49.0 / 4.11.8-2-default, LLVM 4.0.1) GL_VERSION: 3.0 Mesa 17.1.5 ======================================================= [build] use-vbo=false: FPS: 1942 FrameTime: 0.515 ms [build] use-vbo=true: FPS: 2046 FrameTime: 0.489 ms [texture] texture-filter=nearest: FPS: 1927 FrameTime: 0.519 ms [texture] texture-filter=linear: FPS: 1914 FrameTime: 0.522 ms [texture] texture-filter=mipmap: FPS: 2008 FrameTime: 0.498 ms [shading] shading=gouraud: FPS: 1749 FrameTime: 0.572 ms [shading] shading=blinn-phong-inf: FPS: 1730 FrameTime: 0.578 ms [shading] shading=phong: FPS: 1740 FrameTime: 0.575 ms [shading] shading=cel: FPS: 1736 FrameTime: 0.576 ms [bump] bump-render=high-poly: FPS: 1261 FrameTime: 0.793 ms [bump] bump-render=normals: FPS: 2028 FrameTime: 0.493 ms [bump] bump-render=height: FPS: 2057 FrameTime: 0.486 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1774 FrameTime: 0.564 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 1034 FrameTime: 0.967 ms [pulsar] light=false:quads=5:texture=false: FPS: 1870 FrameTime: 0.535 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 699 FrameTime: 1.431 ms [desktop] effect=shadow:windows=4: FPS: 1070 FrameTime: 0.935 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 746 FrameTime: 1.340 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 1123 FrameTime: 0.890 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 811 FrameTime: 1.233 ms [ideas] speed=duration: FPS: 1459 FrameTime: 0.685 ms [jellyfish] <default>: FPS: 1145 FrameTime: 0.873 ms [terrain] <default>: FPS: 133 FrameTime: 7.519 ms [shadow] <default>: FPS: 591 FrameTime: 1.692 ms [refract] <default>: FPS: 179 FrameTime: 5.587 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 1723 FrameTime: 0.580 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 1730 FrameTime: 0.578 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 1730 FrameTime: 0.578 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 1730 FrameTime: 0.578 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 1691 FrameTime: 0.591 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1730 FrameTime: 0.578 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1730 FrameTime: 0.578 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 1027 FrameTime: 0.974 ms ======================================================= glmark2 Score: 1450 ======================================================= </nowiki></pre> =lapx - Leap 42.3= <pre><nowiki> pvdm@lapx:~> glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: X.Org GL_RENDERER: Gallium 0.4 on AMD TURKS (DRM 2.49.0 / 4.4.76-1-default, LLVM 3.8.0) GL_VERSION: 3.0 Mesa 17.0.5 ======================================================= [build] use-vbo=false: FPS: 1949 FrameTime: 0.513 ms [build] use-vbo=true: FPS: 2050 FrameTime: 0.488 ms [texture] texture-filter=nearest: FPS: 1909 FrameTime: 0.524 ms [texture] texture-filter=linear: FPS: 1896 FrameTime: 0.527 ms [texture] texture-filter=mipmap: FPS: 1993 FrameTime: 0.502 ms [shading] shading=gouraud: FPS: 1749 FrameTime: 0.572 ms [shading] shading=blinn-phong-inf: FPS: 1741 FrameTime: 0.574 ms [shading] shading=phong: FPS: 1727 FrameTime: 0.579 ms [shading] shading=cel: FPS: 1740 FrameTime: 0.575 ms [bump] bump-render=high-poly: FPS: 1259 FrameTime: 0.794 ms [bump] bump-render=normals: FPS: 2089 FrameTime: 0.479 ms [bump] bump-render=height: FPS: 2066 FrameTime: 0.484 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1773 FrameTime: 0.564 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 1035 FrameTime: 0.966 ms [pulsar] light=false:quads=5:texture=false: FPS: 1880 FrameTime: 0.532 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 681 FrameTime: 1.468 ms [desktop] effect=shadow:windows=4: FPS: 1069 FrameTime: 0.935 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 743 FrameTime: 1.346 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 1186 FrameTime: 0.843 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 815 FrameTime: 1.227 ms [ideas] speed=duration: FPS: 1511 FrameTime: 0.662 ms [jellyfish] <default>: FPS: 1140 FrameTime: 0.877 ms [terrain] <default>: FPS: 133 FrameTime: 7.519 ms [shadow] <default>: FPS: 587 FrameTime: 1.704 ms [refract] <default>: FPS: 181 FrameTime: 5.525 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 1698 FrameTime: 0.589 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 1712 FrameTime: 0.584 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 1702 FrameTime: 0.588 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 1716 FrameTime: 0.583 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 1710 FrameTime: 0.585 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1703 FrameTime: 0.587 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1708 FrameTime: 0.585 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 1018 FrameTime: 0.982 ms ======================================================= glmark2 Score: 1450 ======================================================= </nowiki></pre> =tecra - tumbleweed= <pre><nowiki> pvdm@tecra:~> glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: Intel Open Source Technology Center GL_RENDERER: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) GL_VERSION: 3.0 Mesa 17.1.5 ======================================================= [build] use-vbo=false: FPS: 966 FrameTime: 1.035 ms [build] use-vbo=true: FPS: 1050 FrameTime: 0.952 ms [texture] texture-filter=nearest: FPS: 1001 FrameTime: 0.999 ms [texture] texture-filter=linear: FPS: 1006 FrameTime: 0.994 ms [texture] texture-filter=mipmap: FPS: 990 FrameTime: 1.010 ms [shading] shading=gouraud: FPS: 987 FrameTime: 1.013 ms [shading] shading=blinn-phong-inf: FPS: 981 FrameTime: 1.019 ms [shading] shading=phong: FPS: 990 FrameTime: 1.010 ms [shading] shading=cel: FPS: 991 FrameTime: 1.009 ms [bump] bump-render=high-poly: FPS: 770 FrameTime: 1.299 ms [bump] bump-render=normals: FPS: 1065 FrameTime: 0.939 ms [bump] bump-render=height: FPS: 1058 FrameTime: 0.945 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 814 FrameTime: 1.229 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 666 FrameTime: 1.502 ms [pulsar] light=false:quads=5:texture=false: FPS: 1033 FrameTime: 0.968 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 486 FrameTime: 2.058 ms [desktop] effect=shadow:windows=4: FPS: 607 FrameTime: 1.647 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 483 FrameTime: 2.070 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 450 FrameTime: 2.222 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 509 FrameTime: 1.965 ms [ideas] speed=duration: FPS: 948 FrameTime: 1.055 ms [jellyfish] <default>: FPS: 896 FrameTime: 1.116 ms [terrain] <default>: FPS: 146 FrameTime: 6.849 ms [shadow] <default>: FPS: 695 FrameTime: 1.439 ms [refract] <default>: FPS: 255 FrameTime: 3.922 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 903 FrameTime: 1.107 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 909 FrameTime: 1.100 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 904 FrameTime: 1.106 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 906 FrameTime: 1.104 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 889 FrameTime: 1.125 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 841 FrameTime: 1.189 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 886 FrameTime: 1.129 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 886 FrameTime: 1.129 ms ======================================================= glmark2 Score: 817 ======================================================= </nowiki></pre> =AMD64 with AMD K8 6600= <pre><nowiki> @amd64:.../~> glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: X.Org GL_RENDERER: Gallium 0.4 on AMD ARUBA (DRM 2.49.0 / 4.4.76-1-default, LLVM 3.8.0) GL_VERSION: 3.0 Mesa 17.0.5 ======================================================= [build] use-vbo=false: FPS: 2017 FrameTime: 0.496 ms [build] use-vbo=true: FPS: 2523 FrameTime: 0.396 ms [texture] texture-filter=nearest: FPS: 2134 FrameTime: 0.469 ms [texture] texture-filter=linear: FPS: 2117 FrameTime: 0.472 ms [texture] texture-filter=mipmap: FPS: 2285 FrameTime: 0.438 ms [shading] shading=gouraud: FPS: 2001 FrameTime: 0.500 ms [shading] shading=blinn-phong-inf: FPS: 2028 FrameTime: 0.493 ms [shading] shading=phong: FPS: 2026 FrameTime: 0.494 ms [shading] shading=cel: FPS: 2018 FrameTime: 0.496 ms [bump] bump-render=high-poly: FPS: 1560 FrameTime: 0.641 ms [bump] bump-render=normals: FPS: 5105 FrameTime: 0.196 ms [bump] bump-render=height: FPS: 5021 FrameTime: 0.199 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 3158 FrameTime: 0.317 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 1684 FrameTime: 0.594 ms [pulsar] light=false:quads=5:texture=false: FPS: 4463 FrameTime: 0.224 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 1009 FrameTime: 0.991 ms [desktop] effect=shadow:windows=4: FPS: 1508 FrameTime: 0.663 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 690 FrameTime: 1.449 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 859 FrameTime: 1.164 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 825 FrameTime: 1.212 ms [ideas] speed=duration: FPS: 1663 FrameTime: 0.601 ms [jellyfish] <default>: FPS: 1703 FrameTime: 0.587 ms [terrain] <default>: FPS: 183 FrameTime: 5.464 ms [shadow] <default>: FPS: 1091 FrameTime: 0.917 ms [refract] <default>: FPS: 227 FrameTime: 4.405 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 5619 FrameTime: 0.178 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 5596 FrameTime: 0.179 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 5607 FrameTime: 0.178 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 3519 FrameTime: 0.284 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 2909 FrameTime: 0.344 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 3469 FrameTime: 0.288 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 3468 FrameTime: 0.288 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 3284 FrameTime: 0.305 ms ======================================================= glmark2 Score: 2526 ======================================================= </nowiki></pre> =AMD64 with Ryzen R5 5500 with NVIDIA GT730= <pre><nowiki> 20230312 @amd64:~> glmark2 ======================================================= glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: NVIDIA Corporation GL_RENDERER: NVIDIA GeForce GT 730/PCIe/SSE2 GL_VERSION: 4.6.0 NVIDIA 470.161.03 ======================================================= ======================================================= glmark2 Score: 1483 ======================================================= </nowiki></pre> 414bd6cf656c477538f2b530696090f46afeffd9 0 608 2737 2023-09-02T10:08:08Z Pvdm 2 Created page with "=Use an NAB test tape to calibrate an IEC deck= *Play the NAB tape on the IEC deck. I am assuming a 15 ips speed. *Play a 1K test tone on the deck and make that your zero reference. *Play the 8K tone and adjust for -2.5dB relative to your 1K tone. *Play the 50Hz tone on the tape and adjust for a +3 dB level if your test tape has fringing compensation. If no fringing compensation, adjust for +4 dB level. =or the opposite= *Use 1K or 500Hz for your zero reference. *..." wikitext text/x-wiki =Use an NAB test tape to calibrate an IEC deck= *Play the NAB tape on the IEC deck. I am assuming a 15 ips speed. *Play a 1K test tone on the deck and make that your zero reference. *Play the 8K tone and adjust for -2.5dB relative to your 1K tone. *Play the 50Hz tone on the tape and adjust for a +3 dB level if your test tape has fringing compensation. If no fringing compensation, adjust for +4 dB level. =or the opposite= *Use 1K or 500Hz for your zero reference. *Play 8K tone and adjust for +2.5 dB *Play 50 tone and adjust for -3 dB (if your tape has fringing compensation. If no FR, adjust for -2 dB) *(+2.7 dB for 10K) 84b590dd2fa94c3720cd1d37efcc38a17bc7bda3 0 8 2741 1865 2023-11-19T15:02:02Z Pvdm 2 wikitext text/x-wiki *[[recover mybb account]] *[[OLD:How to secure an initial MySQL installation]] *[[Database dump & restore]] *[[Securing the initial mysql installation]] *[[How to check database]] *[[How to repair a crashed table]] *[[Allowing access from other hosts]] *[[How to get a list of permissions of mysql users]] *[[Sample commands]] f9851a6ea40fa0b43bede3b8220596e7488f99cf 0 609 2743 2742 2023-11-19T15:04:28Z Pvdm 2 wikitext text/x-wiki goto mysql; ga naar database; execute: UPDATE `mybb_users` SET `salt` = ' ', `password` = 'YOUR_PASSWORD' WHERE `uid` = '1'; waarbij mybb_users de usertabel is en hopelijk de admin account id 1 heeft (en let op de backticks!!) babc5141bdac33d022c41cb615e9e4b0ddba70ea 0 457 2747 2584 2023-11-22T08:54:50Z Pvdm 2 /* De instellingen */ wikitext text/x-wiki ==Inleiding== Met het programma Postfix op een linux systeem kan mail verzonden en verstuurd worden. Er zijn een paar instellingen die soms gedaan moeten worden. Tevens het gebruik van het lokale mailprogramma wordt in deze hoofdstuk uitgelegd (mail,nail,mailx) ==De instellingen== De instellingen die belangrijk zijn om via Postfix mail te kunnen versturen staan in '/etc/postfix/main.cf'. De volgende instellingen zijn belangrijk: myhostname="fully qualified hostname" relayhost=bla.nl De laatste instelling is verplicht. Indien deze parameter niet gevuld is, wordt de mail niet verstuurd naar de ontvanger (postfix zoekt dan zelf de relayhost op via het 'mx-record' van het domein, wat een mail relay host teruggeeft die niet relayed -XXXXX ) ==Mail manipulaties== Nu kan er dus mail verstuurd worden vanaf de host met het commando 'mail' of 'nail'. Dit kan interactief of scriptsgewijs. Een aantal voorbeeldscriptjes zijn: nail -s "subject" -r "afzender" "mailadres" -a "attachment" << EOF bla body bla groetje EOF mail bla@amsterdam.nl -s 'hallootjes' -r joop@bla.tk < /proc/cpuinfo mail bla@amsterdam.nl -s 'hallootjes' -r joop@bla.tk -a attachment < /proc/cpuinfo of simpeler: mail -s "subject" "mailadres" </temp/vandaag.log ===Interactief gebruik van mail=== Als je interactief gebruik maakt van het programma 'mail', zijn er een aantal spelregels (voor de 'mail' of 'nail' prompt) . Als er bijv. 389 mailtjes zijn kun je het laatste mailtje lezen door gewoon '389' in te typen op de prompt. Verlaat met 'q' Ander handige commando's zijn: save --> bewaar de gelezen mail, de uitvoer geeft aan waar de mail terechtkomt (bijv. '/root/mbox') help --> geeft aan hoe je een mail kan versturen list --> laat alle commando's zien (een soort help maar dan uitgebreider) next --> ga naar het volgende mailtje d 1 --> delete mail 1 '''d 1-300 --> delete mail 1 t/m 300''' header --> laat de lijst met mail zien q --> verlaat de applicatie ==De mailboxen== De postfix mailbox is opgeslagen in de directory '/var/spool/mail/"username". De gelezen en opgeslagen mail (gaat automatisch bij het afsluiten) staat in "user_home_dir"/mbox. ==De postfix deliveryqueue legen/flushen== #postqueue -f <-- waarschijnlijk niet het goede commando #postsuper -d <queueID> Alles verwijderen: #postsuper -d ALL Het queueID kun je vinden met #postqueue -p ==Alle systeem mail for root verwijderen== echo 'd*' | mail -N ==De postfix queue bekijken== #mailq of #postqueue -p =Een werkende postfix configuratiefile main.cf= Hier volgt een goed werkende file voor de transparent mail relay host cups: <pre> relay_domains = $mydestination, hash:/etc/postfix/relay virtual_alias_maps = hash:/etc/postfix/virtual #virtual_uid_maps = static:303 #virtual_gid_maps = static:303 #virtual_minimum_uid = 303 #virtual_mailbox_base = /srv/maildirs #virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf #virtual_mailbox_limit = 0 #virtual_mailbox_limit_inbox = no #virtual_mailbox_limit_maps = hash:/etc/postfix/vquota #virtual_mailbox_limit_override = yes #virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf #virtual_transport = virtual ## Additional for quota support #virtual_create_maildirsize = yes #virtual_mailbox_extended = yes ### Needs Maildir++ compatible IMAP servers, like Courier-IMAP #virtual_maildir_filter = yes #virtual_maildir_filter_maps = hash:/etc/postfix/vfilter #virtual_mailbox_limit_maps = mysql:/etc/postfix/mysql_virtual_mailbox_limit_maps.cf #virtual_mailbox_limit_override = yes #virtual_maildir_limit_message = Sorry, the user's maildir has overdrawn his diskspace quota, please try again later. #virtual_maildir_limit_message_maps = hash:/etc/postfix/vmsg #virtual_overquota_bounce = yes #virtual_trash_count = yes #virtual_trash_name = ".Trash" ############################################################ # End MySQL from postfixwiki.org ############################################################ inet_protocols = all biff = no mail_spool_directory = /var/mail canonical_maps = hash:/etc/postfix/canonical virtual_alias_domains = hash:/etc/postfix/virtual relocated_maps = hash:/etc/postfix/relocated transport_maps = hash:/etc/postfix/transport sender_canonical_maps = hash:/etc/postfix/sender_canonical masquerade_exceptions = root masquerade_classes = envelope_sender, header_sender, header_recipient myhostname = bla.wzs.amsterdam.nl delay_warning_time = 1h message_strip_characters = \0 program_directory = /usr/lib/postfix inet_interfaces = xxx #inet_interfaces = localhost masquerade_domains = mydestination = $myhostname, localhost.$mydomain defer_transports = mynetworks = xxx #mynetworks_style = subnet disable_dns_lookups = no relayhost = smtprelay.basis.lan content_filter = mailbox_command = mailbox_transport = strict_8bitmime = no disable_mime_output_conversion = no smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_client_restrictions = permit_mynetworks smtpd_helo_required = no smtpd_helo_restrictions = strict_rfc821_envelopes = no smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination smtp_sasl_auth_enable = no smtpd_sasl_auth_enable = no smtpd_use_tls = no smtp_use_tls = no smtp_enforce_tls = no alias_maps = hash:/etc/aliases mailbox_size_limit = 0 message_size_limit = 0 c1cf13dceadec57414e0475262cde087316e3d24 0 529 2750 2749 2023-11-22T16:14:17Z Pvdm 2 /* initialiseren van een DCC tape / initialize a DCC tape */ wikitext text/x-wiki =when is the tape/datapath ok?= "A much better indication for the quality of the datastream is the TAPE BLOCK COUNTER ffff. If the counter is reset every minute the signal processing path should be ok. One minute of uninterrupted error-free data blocks gives a count of 1200. In case of too high error rates (frequent resets) check the signal flow DCC Head -> read amp -> DEQ -> DDSP (esp. RDMUX)" =initialiseren van een DCC tape / initialize a DCC tape= Initialiseren van nieuwe bandjes, of een DCC bandje nieuw opnemen: # DCC450: REWIND, then APPEND and REC/MUTE to start. *DCC600: REWIND, then press APPEND. *DCC730 & 951: REWIND, then REC SELECT/PAUSE. Initialize new DCC tapes, or make DCC tapes new again: *DCC600: REWIND, then press APPEND *DCC730 & 951: REWIND, then REC SELECT/PAUSE =probleempiep= Na het onderzoeken en oplossen van het gepiep van een dcc cassette, https://nl.wikipedia.org/wiki/Digital_compact_cassette, ben ik eens gaan onderzoeken waarom een dcc cassette vastloopt in een dcc speler. Aanleiding was de koop op marktplaats van een dcc 600 recorder met een aantal opneembare en voorbespeelde dcc cassettes. De verkoper werd gek van het gepiep en vastlopen van de recorder. Hij had destijds zelfs een nieuw loopwerk bij philips op de kop kunnen tikken. Voor hem vrij makkelijk want hij werkte bij philips. Dit loopwerk heeft hij vervangen en wat bleek: de bandjes bleven vastlopen. Uiteindelijk staat heel de boel hier op de werkbank. Hij deed de hele boel van de hand van ellende. =cassettes= De koppen en het loopwerk heb ik om te beginnen maar eens goed gereinigd. Om zeker te weten dat de recorder goed werkt, heb ik mijn eigen cassettes gedraaid. Deze liepen niet vast. Dan moet het aan de cassettes liggen, zou je zeggen. ==openen== Om te beginnen maar eens een opneembare cassette geopend. Dit is niet een eenvoudige zaak, daar je eerst het veertje moet ontgrendelen van het schuifbare metalen klepje. De twee helften zitten vervolgens in elkaar geklikt. Deze zijn met wat voorzichtig beleid wel uit elkaar te halen. Bij het openen van de cassette komt een folie los die je los kunt verwijderen. De twee helften liggen naast elkaar op de werkbank. Nu zien we het verschil tussen een gewone analoge cassette en een digitale cassette. Beiden hebben natuurlijk een viltje in het midden van de tape die de band tegen te kop duwt. Deze veroorzaakt vaak een pieptoon, dit is bekend. =viltje= Aan de zijkanten links en rechts achter de witte rollertjes zit bij een dcc echter ook een viltje. Deze zorgen voor een stabielere loop van de digitale tape. Bij analoge cassettes zijn deze viltjes niet aanwezig. Deze viltjes zijn meteen ook het probleem van het vast lopen van de cassettes. Dus niet het viltje wat tegen de kop duwt!.De recorder krijgt de tape hier niet doorheen geduwd. Dus loopt hij vast. Ook dit geeft een piep toon.Deze viltjes hebben schijnbaar een vette substantie omdat een weinig gebruikte voorbespeelde dcc dit probleem ook geeft. =reinigen= Na verloop van tijd als je de cassettes lang niet gebruikt geven deze viltjes een vette plek achterop de tape. Dus precies achter het viltje, zowel links als rechts.(linker en rechter viltje) Dit kun je zien door de tape een klein beetje uit de cassette te trekken. Een donker plekje op de tape blijft achter. Met videospray cleaner 90 en een wattenstaaf kun je deze plek verwijderen. Alcohol is lastig omdat deze toch wat achter laat op de tape.Je mag dus niets meer op de tape zien. Hoe langer je de tape niet gebruikt des te vetter wordt die plek achter het viltje. =weer in elkaar= Na reinigen heb ik de cassette weer in elkaar gezet. Het in elkaar zetten is ook wat lastig omdat ook het veertje wat het metalen beschermkapje bedient op de juiste manier terug moet worden gezet. Als de cassette in elkaar zit, blijkt dat het vastlopen over is. Hetzelfde probleem ontstaat met voorbespeelde cassettes, ook hier plekjes achterop de tape als je de cassette lang niet gebruikt hebt. Bij mijn eigen cassettes heb ik dit probleem ook aangetroffen, daar ik niet regelmatig dcc cassettes draai en dus cassettes lang laat liggen zonder dat deze zijn teruggespoeld. =conclusie= Conclusie van dit verhaal is: Laat dcc cassettes niet te lang liggen als deze niet zijn teruggespoeld. Spoel je ze terug dan ontstaat dat probleem niet omdat dan de aanlooptape achter de viltjes zit. De viltjes zitten net links en rechts achter de witte geleiderol. Al mijn cassettes met dat probleem heb ik kunnen reinigen. Je hoeft natuurlijk niet steeds de cassette uit elkaar te halen. Tape kun je ook zo uit de cassette halen met een pincet. Het uit elkaar halen van de cassette was bedoeld om te kijken hoe dat probleem ontstaat. =wit vs. bruin= Ik heb inderdaad het idee dat de witte viltjes eerder piepen dan de bruine viltjes. Het lijkt erop dat witte viltjes meer vuil oppikken dan de zwarte. De bruine zijn ook van een harder materiaal gemaakt lijkt het en daardoor minder bevattelijk voor vuil. Ik heb hier ook cassettes liggen met zwarte viltjes, deze zijn echt harder.Bij de productie dus al wijzigingen doorgevoerd. De viltjes in de cassette welke links en rechts zitten zijn ook wit. Ik heb zelf alle cassettes teruggespoeld naar het begin of het einde. Het vastloop probleem deed zich bij mij dus ook voor. Een nieuwe dcc had ik eenmaal tot halverwege gedraaid. Daarna niet meer gebruikt en na een lange tijd zat deze dus ook vast. Je zag precies aan de achterkant op de tape een vetplek zitten van het viltje dat niet vuil was. Deze geven dus standaard af op de tape. Ze doen dit niet na korte tijd, en na langere tijd zie je de tape op die plek wat golven. Zowel voorbespeeld als opneembare dcc,s hebben hier last van. Waarschijnlijk is dit ook de reden dat veel eigenaren met een dcc951 problemen krijgen met het apparaat. En trouwens ook de dcc 900. Een dcc 951 geeft dan aan dat de kop gereinigd moet worden, terwijl het probleem in de cassette zelf zit. Voordat je denkt dat een drukrol versleten is of snaar slecht is, moet je zeker weten dat de cassette welke je in het apparaat stopt , goed is. Piepgeluiden in het middelste viltje geven daardoor ook de nodige problemen. je denkt al snel dat dat piepen uit de recorder komt. Philips heeft deze problemen niet meer opgelost, omdat het systeem in 1996 gestopt is. Alleen zag je dat er zwarte ipv witte viltjes gebruikt werden.Ze hebben deze problemen waarschijnlijk op het laatst ook waargenomen. Mooi voor ons deze problemen verder op te lossen. Aandrukviltje bij de kop schoonmaken met IPA en wattestaafje, ook wat opruwen en pluizig maken, zodat er geen plakkende laag onstaat. Bron: http://forum.mfbfreaks.com/ a8695baca67d850d282011acc8906e92cd5ab57b 0 610 2753 2752 2024-01-24T16:54:48Z Pvdm 2 wikitext text/x-wiki Install FLAC package, then metaflac will be present. #root@moode:/mnt/SDCARD# metaflac --set-tag ARTIST="David Axelrod" holythursday.flac #root@moode:/mnt/SDCARD# metaflac --set-tag TITLE="Holy Thursday" holythursday.flac #metaflac --list my_music.flac 89108222dbdefee97ad7150cb42a971fb94fe7dc 0 530 2759 2746 2024-01-31T07:49:55Z Pvdm 2 /* Maintenance of a Philips DCC600: */ wikitext text/x-wiki =Onderhoud van een Philips DCC600:= * rechthoekige ladebovenklep eraf schroeven (ligt OP de cassette. TORX 6 nodig) en dan kun je bij de kop: goed schoonmaken met wattenstaafje en IPA. Let op: kop is zeer fragiel. * rechthoekige bovenlade heeft 3 witte/gele nylon wieltjes: schoonmaken. * de 2 kleine aandrukrolletjes eruit wippen en schoonmaken met IPA en daarna een nacht in verzadigde afwas laten weken. * de 2 snaren vervangen: lade en loopwerk. ** de snaar van de lade is vierkant: 80 mm diameter en 1 a 1,3 mm dik. ** de snaar van het loopwerk is 3,5x0,5x150mm (breedte x dikte x lengte platgedrukt). * de 2 capstans reinigen (IPA). * loopvlak (zwart, op de 2 wielen) van de capstan-riemen schoonmaken. * loopwerk smeren. * eventueel druppeltje olie in de motoren. * Het soldeerwerk van de voeding nalopen. -servicemode aanzetten: dolby - play - en dan rec/pause indrukken. Laat o.a. dropouts zien. -Er kan een probleem met de voeding zijn, losse pootjes van spanningsregelaars -Vaak is de print zekering van t3.15ma op het main board defect. Deze gaat erdoor omdat de oude snaar vastplakt aan 1vd vliegwielen. -Het LDU-1000 loopwerk zit in de DCC300, DCC380, DCC600 en de DCC450. -Zie ook de Repair database onderaan de pagina [[File:Aandrukrol_DCC600.gif|400px]] == =Modifications= <pre>Looking at the manual...... PSU board Caps 2215, 2216, 2217 replace with same voltage larger uF caps. These are the PSU reservoir caps. Prob replace 2211 2213 with same value uF. Probably limited by physical size here. Something like Panasonic FR or FC or TSUP if they fit. Digital board On the digital board, replace all the elcos with OsCon SEPC solid polymer much higher uF like 470uf 6.3v unless they are doing a specific job other than PSU. Check with the manual. Analogue output stage 2257, 2258 2259 2260 are elco's in the signal path - replace with 4.7uf film caps like WIMA MKS2 (tiny with 5mm lead spacing) and very good. Opamp 7305 replace with dual opamp of choice (LME49720 is my choice) and see if you can get some local elco's on the PSU pins 2351 & 2352 in the feedback loop with 470 pf Silver mica Obviously do a bit at a time and listen in between........ These mods are suggested based on general experience modifying similar equipment and not the DCC600 directly...... </pre> =Maintenance of a Philips DCC600:= * unscrew the rectangular drawer top cover (is located on top of the cassette, TORX 6 required) and then you can access the head: clean well with cotton swab and IPA. Note: head is very fragile. * rectangular top drawer has 3 white / yellow nylon wheels: clean. * flip out the 2 small pressure rollers and clean with IPA and then soak overnight in saturated detergent. * replace the 2 strings: drawer and running gear. ** the belt of the drawer is square: 80 mm diameter, or 130 mm flat, and 1 mm thick. ** the belt of the running gear is 3.5x0.5x150mm (width x thickness x length flat). * clean the 2 capstans (IPA). * clean the tread path (black, on the 2 wheels) of the capstan belts. * lubricate running gear. * maybe drop of oil in the engines. * Check the solderings in the power supply board. -potential problem with the Power Supply. Voltage regulators with loose legs. Resolder. -often the fuse t3.15ma on the mainboard is defect. =engage servicemode= To engage servicemode : dolby - play - and then press rec/pause. Shows the dropouts etc. =OFFICIAL PHILIPS REPAIR DATABASE:= <pre> MODEL: DCC600 SYMPTOM: The display does not light up at all. CURE: Check the -30V. If not available, check T7201 (4822 130 41327). MODEL: DCC600 SYMPTOM: Totally inoperative. CURE: Check solder joints of mainsswitch S1204. MODEL: DCC600 SYMPTOM: Totally inoperative. (No display and no functions) CURE: Check the main and front uP. MODEL: DCC600 SYMPTOM: No tape transport. The capstan motor does not run. CURE: Check for short circuit in the deck motor PCB. MODEL: DCC600 SYMPTOM: Digital no sound, analog weak, reading and winding all the time. CURE: Clean the head. MODEL: DCC600 SYMPTOM: DCC sound interrupting. CC plays O.K. CURE: Check Dig. PCB (4822 214 33899). MODEL: DCC600 SYMPTOM: On Playback of DCC tapes the Audio drops out. CURE: Set up as per the Service Manual the CASS motor speed (3264) MODEL: DCC600 SYMPTOM: No recording, play back O.K. CURE: Check digital PCB. Codenr. 4822 214 33899 MODEL: DCC600 SYMPTOM: Stops playing DCC tapes after a few seconds. CURE: Check whether connector 1327 is mounted well. MODEL: DCC600 SYMPTOM: Totally inoperative after some time. CURE: Check transistor T7349. MODEL: DCC600 SYMPTOM: The digital sound is sometimes interrupted. CURE: Replacing the digital printed board will solve the problem. The service codenumber of this board reads: 4822 214 33899. REMARKS : All sets from production week 9323 onwards have been modified. MODEL: DCC600 SYMPTOM: First 200 msec. no sound after next and prevous. CURE: Replace main processor to software version V72. MODEL: DCC600 SYMPTOM: Sometimes no sound on right speaker. CURE: Check Dig.PCB 4822 214 33899. MODEL: DCC600 SYMPTOM: Sound distorsion by interfering of a TV set. CURE: When the set is placed in the neighbourhood of a TV set (K40 type) the sound from the DCC is distorted. The distortion disappears as soon as the TV set is switched-off. As all DCC recorder complies the Philips requirements concerning magnetic fields it is advised to rearrange the set-up. It is known that some strong fields will interfere with the head connections. For this reason in the IFU is published: Do not place the DCC...near magnetic fields ... , ..) Placing the DCC at the other side of the TV-set (away from the high voltage transformer) can solve the problem. Adding an additional metal screen is also possible but is not a 'nice' solution in a home set-up. MODEL: DCC600 SYMPTOM: After about 5 minutes, set stops playing and relay starts clicking. CURE: Check IC7711 (PLC) 4822 209 31993. MODEL: DCC600 SYMPTOM: After some time noisy sound. CURE: Check digital PCB. It might be that ADC (AK5326) is heat sensitive. Replace digital PCB. (4822 214 33899) MODEL: DCC600 SYMPTOM: Sometimes middle and right-hand segments of display are failing. CURE: Check solder joints of the front processor and the FTD. MODEL: DCC600 SYMPTOM: Distortion of TV signal when DCC is in Play mode. CURE: Add screening (item 568) between DCC loader part and transformer/supply part. MODEL: DCC600 SYMPTOM: In some cases DCC cleaning cassette SBC3500 does not work properly. CURE: This problem is caused by a too long capstan (marginal difference compared with DCC900) which carries the cleaning cassette from the inside. In this case the DCC sensor switches are not activated and cassette is not accepted. Either fix a piece of adhesive tape at the bottom side of the cassette housing or drill a hole of 4.5 mm through the housing. REMARKS : Existing stock of Philips Service Warehouse is being reworked by drilling the hole. New stock will arrive with a thinner housing at the position the capstan is touching the housing. MODEL: DCC600 SYMPTOM: The player is reading and winding continuously. CURE: Check digital PCB (4822 214 33899) MODEL: DCC600 SYMPTOM: Too much wow and flutter on side A. CURE: Check pressure roller side A. MODEL: DCC600 SYMPTOM: After some time maximum error rate. CURE: Check digital PCB (DDSP IC7506 temperature sensitive ?). Service codenumber digital PCB is 4822 214 33899. MODEL: DCC600 SYMPTOM: Noisy and weak sound on the left channel with ACC. DCC OK. CURE: Tape drive unit defective. Replace tape drive unit. MODEL: DCC600 SYMPTOM: Does not play DCC cassettes. Max. error rate after cleaning head CURE: Replace the tape drive unit. MODEL: DCC600 SYMPTOM: Scratching sound audible when switching on. CURE: Check motor holder pos. 120 (4822 256 92024). MODEL: DCC600 SYMPTOM: Display inoperative. No light in the display. CURE: No -30V. Check safety resistor R3203. MODEL: DCC600 SYMPTOM: Transistor 7355 (BC817/40) in solenoid control circuit defective. CURE: Replace defective transistor by a new one (4822 130 42615). Check soldering of diode 6308 (BAS16) and the functioning of transistor 7205 (BD434) on main board. Check also the cooling of transistor 7205 on main board. REMARKS : Insufficient pressure of transistor clips will cause an increasing supply voltage of the play magnet (voltage on solenoid > 15V), which can destroy transistor 7355. MODEL: DCC600 SYMPTOM: Audio recorded on digital tape, no time or track nr. recorded. CURE: By replacing the tape deck mechanism it was found that this was actually causing the fault. Codenr. 4822 691 20833. MODEL: DCC600 SYMPTOM: Sometimes the use-again marker not found on customer recorded DCC. CURE: (Endless loops during append) Cut off minus lead of Electrolytic Capacitor 2711 on read/write board. Solder wire from minus lead of 2711 to pin 11 of IC 7703 (Read amplifier TDA1317). REMARKS : This phenomenon occurs only on Printed Circuit Boards with production stage .4 and is caused by crosstalk from WDATA to INAUX signal line. MODEL: DCC600 SYMPTOM: Set comes in a hang-up situation. CURE: The reset circuit has been improved to prevent hang-up, by changing item 3419 (refer to service manual page 48, mapping code M12) from 47k into 4k7 (4822 051 20472). (From productionweek 9316 onwards.) MODEL: DCC600 SYMPTOM: At first time cassette plays normally, second time set stops. CURE: Second time set stops in the middle of cassette. Resolder resistor 3263. Maybe this chip resistor 3263 was not good soldered and sometimes it does not make contact. This results in failing of the capstan motor. CAUSE : Temporally this resistor was hand mounted. From week 9312 onwards this mounting process has been changed. MODEL: DCC600 SYMPTOM: Noisy tray, squeaking sound during open/close CURE: Grease guiding parts of drawer pos. 209 resp. catch lever assembly pos. 216. with Molykote, service code 4822 390 20139. MODEL: DCC600 SYMPTOM: Poor loading function CURE: Slider opener (pos. 216-219 of Exploded View) lands on top of cassette. REASON: Shutter (pos. 552) out of form. Left side touches either bracket (pos. 551) or controlling lever (pos. 556). SOLUTION: Bend left side of shutter so, that there is no contact to other parts (min. distance between pos. 551 and pos. 552>= 0,1mm). REMARKS: Loading assemblies, marked with a red cross on the top of bracket 551, are already checked by the factory. MODEL: DCC600 SYMPTOM: Cassette gets stuck behind the front when lifted at left side CURE: This occurs when cassette is lifted at left side in order to remove it from the opened tray. The switch is opened/closed by a ridge, located at the back righthand corner of the drawer. To delay the switch actuation cut off some plastic of the ridge. Attention: This modification also takes an influence on the feature touch to close. If too much plastic is removed the tray might already close while a cassette is inserted ! Try to find an optimal compromise. CAUSE: The drawer (pos. 209) does not open far enough, because the tray-out switch (pos. 1437) is actuated too early. REMARKS: This publication will be followed by a service information. MODEL: DCC600 SYMPTOM: When using an ACC (analogue cassette) the drawer does not open. CURE: Plastic edge inside loading causes an analog cassette to get stuck. Remove the plastic edge. MODEL: DCC600 SYMPTOM: Drawer does not open. CURE: Check pos.212 (4822 403 70851) MODEL: DCC600 SYMPTOM: Gives DCC with CC cassette. Sometimes cass.blocked. CURE: Slide opener lands on top of cassette. Check position of the mounting tape foot. MODEL: DCC600 SYMPTOM: Updating uPs CURE: Updating uPs During the course of production the uP's in 70DCC300, 70DCC380 and 70DCC600 have been modified. Sets produced between week 9302 and week 9331 have old versions. In case one of the two uP's has to be exchanged in those sets, the other uP has to be replaced too, because in spare parts warehouse only the last versions are taken on stock. From week 9331 onwards front uP (item 7410) reads TMP870M70AF-6123 MASK V67 (available with service code 4822 209 32528). Main uP (item 7335) reads P83C528FBP/054 MASK V69 (available with 4822 209 32974). REMARKS: This publication will be followed by service information a93-362 MODEL: DCC600 SYMPTOM: Service Manual correction Electrical partslist CURE: Service Manual correction Electrical partslist digital board Codenumber for A/D-converter AK5339 (pos. 7514) was 4822 209 31622, should read 4822 209 33849. MODEL: DCC600 SYMPTOM: Guidance form CURE: Guidance form - Next Guidance form is enclosed at repairable unit 4822 691 20833. Please notice the wiring which should be included with the returned unit. GUIDANCE FORM REPAIRABLE UNIT 4822 691 20833 Please fill in this form and return it with the defective unit. TYPENUMBER (Unit demounted from set) : Serial number: COMPLAINT DESCRIPTION: INFORMATION GATHERED VIA SERVICE MODE EXTENDED PLAYMODE (selected via PLAY) WITH ERROR INDICATION (On display): MORE DETAILED OBSERVATIONS : YES NO TRAY LOADING OK DCC SOUND OK ANALOGUE SOUND OK MECHANICAL NOISE OK SPEED OK FRICTIONS OK TAPE TRANSPORT OK Return the defective unit complete assembled according to the drawing on the backside of this paper to: Invoice to: Philips Consumer Electronics B.V. 670005 Consumer Service - Price centre 5600 MD Eindhoven building SBP5 The Netherlands Ship to: Philips Consumer Electronics B.V. 676723 Consumer Service 5600 MD Eindhoven building SDM5 The Netherlands ATT: Mr. C. Lieberwirth CORRECTIVE ACTION/SOLUTION (to be filled in at central repair workshop): Report number: MODEL: DCC600 SYMPTOM: Customer problems when using DCC CURE: Customer problems when using DCC In general playing back pre-recorded DCC-cassettes does not bring problems to users, because playback of such a cassette is more or less simular to operating a CD-player. A number of problems are found in the playing back and/or recording of the user-recorded DCC-cassettes, caused by not proper 'initializing' of ALL these cassettes. Initializing is important because this is closely linked to basic customer-expectations of a digital product: - Track number; - Time indication. The DCC-standard distinguishes 2 different formats of user-recorded DCC-tapes: a. Super-user format b. User format But there are also combinations of the 2 user-recorded formats possible: c. Combinations of the 2 formats. And there is the pre-recorded DCC tape format: d. Pre-recorded DCC SUMMARIZED CHARACTERISTICS: a. Super-user format: - continuous absolute time information available (remaining time is calculated by the set) - Track numbering and track title at start of track are possible. (this means that also renumber is possible) - Initialization required - TOC (Table of Contents) possible at start of track 1 For figures see Audio Service newsletter 63.01 On Display when super-user format is loaded at position a: TRACKTIME - -10:51 b. User format: - No continuous absolute time information available on tape - No track numbering/title. (this means that renumber is not possible) - No initialization required The start markers are only used for track access. On Display when user format is loaded at position b: TRACKTIME : Notice: track is blank! Some DCC typenumbers show counter settings, others the estimated time based on the tacho-signals. c. Combination of the 2 formats. - This format usually happens when the APPEND function is not used. - The APPEND function is designed to guarantee the Super-user format in case a recording is made at the end of a partially recorded tape. When a recording is started on a blank area, the result will always be a User-format. Correction by renumbering is not possible. d. Pre-recorded DCC - Continuous time information available (inclusive absolute time, track time, remaining time etc.) - Track information continuous available - TOC information continuous available - Track title information continuous available. - Display will show on what ever position loaded the track and time information. example: TRACKTIME 210:51 MODEL: DCC600 SYMPTOM: Initialising DCC CURE: Initialising DCC NEW DCC CASSETTE: How to initialize the cassette (= making a lead-in recording at the beginning of the tape) is stated in the Instructions for Use. In the various typenumbers the following keys have to be activated: For DCC091, DCC450: REWIND, APPEND For DCC170: REWIND, REC PAUSE For DCC300, DCC380: REWIND, APPEND For DCC600: REWIND, APPEND For DCC730, DCC951: REWIND, REC SELECT/PAUSE For DCC900: REWIND, APPEND For more details: see Instructions for Use of concerned typenumber; chapter recording. After this initialization the track number and (absolute) time information will be recorded on the user-recorded tape. The above shown survey is a simplified universal applyable operation. The most problems are caused by the fact that users are accustomed to apply the record function straight forward, like recording ACC-cassettes. PARTIALLY RECORDED For all typenumbers, except DCC170: Use APPEND to search for end of last recording in case of partially recorded DCC-tape and so proper coupling of old and new recordings is made. For DCC170: Search Manually for END indication of last recording and make new recordings from that spot onwards. OVERWRITING In case of completely overwriting a user-recorded DCC-tape the initializing procedure has to be performed again! CONCLUSION: It is very important to initialize a user-recorded DCC-tape. If a DCC-tape is initialized or not, can easily be seen on the display information in Play-back mode. Starting at the beginning of the tape track time An empty DCC tape:: Not initialized DCC tape (User format) 11 : 24 Initialized DCC tape (Super-user format)312 : 49 MODEL: DCC600 SYMPTOM: Adjustment head current CURE: Adjustment head current - In case the read/write head of the DCC mechancism should be exchanged and/or the read/write IC's are defective the head current has to be re-adjusted. Because at this moment the needed test equipment is not available, this will be done in a central repair procedure. The following codenumbers are resorted in this repair procedure, at Philips Consumer Service known with code (REPARI 1 and 4): For 70DCC900: The complete tape deck mechanism item service codenumber 001M 4822 691 20777 For 70DCC300, 70DCC380 and 70DCC600: The complete loading mechanism item service codenumber LDU4822 691 20833 and The complete digital board (PCB5) item service codenumber 4822 214 33899 In case of a repair one has to ship, without waiting, the defective item to: Invoice to: Philips Consumer Electronics B.V. 670005 Consumer Service - Price centre 5600 MD Eindhoven building SBP5 The Netherlands Ship to: Philips Consumer Electronics B.V. 676723 Consumer Service 5600 MD Eindhoven building SDM5 The Netherlands ATT: Mr. C. Lieberwirth Please enclose a copy of the invoice inside the carton. The rest of the instructions are according to the PCS repair procedure available at the desk of Mr. Lieberwirth, Repair Manager, Phone +31-40-735509, Fax +31-40-734515 MODEL: DCC600 SYMPTOM: Trackselection CURE: Trackselection Direct track access is meant to search a wanted tracknumber by taking the shortest path to get to the track. Due to the differences in possible tapes, this topic is rather complex: * On a pre-recorded DCC tape, the Table Of Contents is always recorded continuously on the tape. This means that direct track access is possible. When jumping from track 3 to track 8. In this case the side is changed (from A to B) This is the SHORT SEARCH. * On a user-recorded tape, the Table Of Contents (TOC) cannot be recorded continuously. The TOC has be adapted all over the tape as soon as the recording on the tape is changed. For this reason the TOC can only be written at the start of track 1. This means that now jumping from track 3 to 8 results in so called SEQUENCIAL TRACK SEARCH. Jumping from track 3 to track 8 is done via track 4, 5, 6, and 7. In practise it has become clear that when a DCC is loaded, it is in many cases not positioned at the start of track 1. This means that the only alternative is sequential track search: The deck will in some cases not take the shortest path as the location of the required track is unknown. IMPLEMENTATION: DCC900 Writing TOC on user-recorded DCC was planned but did not fit into the microprocessor internal ROM capacity. To delete this possibility from the specification was a last minute decision. Unfortunately the Instruction For Use has not been adapted accordingly. That is why 10-key commands are not accepted (NO TOC message). There is no service solution available. DCC600 Writing TOC on user-recorded tape was also not possible because of the limitations of the microprocessor internal ROM capacity. Lessons are taken from DCC900, that is why the sequential search possibility has been implemented. When a 10-key command is issued and the TOC is not known, the deck will perform this above described sequential search. The result is that DCC600 will in only a few cases not respond to a 10-key command. Due to the fact that the microprocessor of the DCC900 is completely filled and no larger memory is available, a service solution which incorporates sequential search like DCC600 is not possible. MODEL: DCC600 SYMPTOM: Modification speed control CURE: Modification speed control In the course of production the temperature stability circuit of the speed control has been improved. This may influence the compatibility of the LDU1000 loading assy (4822 691 20833). This loading has to match with the various versions of the main pcb because components on PCB3 (main pcb) and PCB6 (dcc-indicator) have been changed. Situation Loading marked LDU1000 WT00 and WT01: PCB3: R3262 (12k) with parallel to it potentiometer 3264 (10k). In series with this 3263 (12k). PCB6: NTC-resistor 3160 (150R) in series with capstan motor. Situation Loading marked LDU1000 WT02: PCB3: R3262 (deleted), potentiometer 3264 (4k7). In series with this potentiometer 3263 (15k). PCB6: Resistor 3160 (100k) in series with diode 6601 (kathode at 3263 and - (MINUS) capstan motor, anode at 3160) parallel to capstan motor. Therefore: In case the loading assy with with printed board PCB6 has to be replaced the built-in main pcb has to be matched to the production stage of the LDU1000 delivered. Replacement procedure: 1)When replacing a Loading marked LDU1000 WT00 or WT01 by a WT02 version, R3263 has to be changed from 12k to 15k! When replacing a Loading marked LDU1000 WT02 by a WT00 or WT01 version, R3263 has to be changed from 15k to 12k! 2)Adjust speed control as described on page 28 of service manual. 3)Check Tape up torque, wow and flutter (for limits see page 28 of Service Manual). 4)Check Analog feedback level and bias. (read/write pcb) 5)Check Dolby level if necessary (main pcb) MODEL: DCC600 SYMPTOM: Codenumber information CURE: Codenumber information DCC Cleaning cassette SBC3500 is from now on available with service codenumber 4822 015 20646. MODEL: DCC600 SYMPTOM: Availability of front boards CURE: Availability of front boards Front boards for DCC-recorders with mounted uP are available now: 70DCC300 : 4822 214 52176 front board 70DCC380 : 4822 214 52177 front board 70DCC600 : 4822 214 52178 front board MODEL: DCC600 SYMPTOM: Correction partslist RED1 Tape Transport CURE: Correction partslist RED1 Tape Transport Capstan motor item 1023 was 4822 361 21506 should read 4822 361 21646. 4822 361 21506 is capstan motor of REN and RER tape decks. MODEL: DCC600 SYMPTOM: Corrections to the service manual CURE: Corrections to the service manual - The service test program (page 25-26) Key test : Correct key to enter this test is 'MARK WRITE' Hole test: This test can only be entered if tray is in opened position. In tray test the tray is moved outside. So first start with tray test before hole test. IR test: RC-5 codes of TEXT and TIME have been exchanged in this publication. RC-5 code for TIME should read '11', RC-5 code for TEXT should read '122'. Adjustment table (page 28) Position number of potentiometer for take-up torque should read 3280. REMARKS: This publication will be followed by service information A93-362 MODEL: DCC600 SYMPTOM: Modification CURE: Modification In course of production the power supply circuitry of the read/write board has been changed: * Double-diode pos. 6703 (BAV99 - 5322 130 34337) has been built-in in series to the voltage stabilizers 7701 and 7702. The double-diode reduces the input voltage of the stabilizers and thus the power dissipation of these ICs. * Voltage stabilizer pos. 7708 has been changed to a type with low voltage drop (LM2931Z-5.0 - 5322 209 60749), capacitor pos. 2764 is changed from 10nF to 10æF (4822 124 23179). Both actions improve the plop-behaviour when the set is powered-off during a recording session from an analog source. REMARKS: Modifications have been taken place in read/write boards from production stage .5 onwards. Production stage can be identified by the last digit of the twelve-figure number, located at the lower right corner of the printed circuit board. fc38c866d1fb4aa36c96df2677786c969ad9d9f8 0 16 2760 2702 2024-02-07T15:34:13Z Pvdm 2 wikitext text/x-wiki *[[test harddisk for bad blocks]] *[[set cpu performance]] *[[determine which vga driver is in use]] *[[rsync root volume]] *[[rescan SCSI bus]] *[[disable cpu core for light work]] *[[detect webcam properties]] *[[bogomips]] *[[RAID]] * [[Garmin Forerunner 305, linux and Garmin Connect]] * [[Speedtouch commands]] * [[enable suspend-to-ram on notebooks with ATI card]] * [[enable harddisk spin-down / sleep mode / standby]] * [[enable monitoring of MD (software RAID) devices]] * [[disable hardware polling for CD-drives]] * [[Linux Software RAID: growing filesystems and adding disks]] * [[ATI graphic chipset overview]] * [[Burning CD/DVD from CLI with wodim]] * [[Verhuis een linux systeem naar nieuwe hardware]] *[[Install Linux on an SSD]] *[[perform bechmarks on the filesystem]] *[[Screenresolutions, dimensions and DPI]] 663c64b2d1fa9501c5098080114867e80c690a8a 0 440 2766 1654 2024-03-15T08:24:46Z Pvdm 2 /* sticky shed syndrome */ wikitext text/x-wiki When reel-to-reel tape was still a studio/consumer product, BASF followed a naming convention that defined the product type. In 1984 it became clear that open reel tape was only going to be a professional product in the future, and the naming convention changed with the introduction of "SM 910"--Studio Master 910. The US market named the consumer products differently, and that accounts for addition confusion. The general run down of products and naming conventions follows. The product type was first defined by a two-letter designation describing the playing length, followed by a number defining the total thickness of the tape in microns. If the tape were back-coated, an "R" for "rueckseite" followed the playing length. The final letters, if they appeared, described the type of coating. <pre> SP 50 = standard play for 50-micron tape with 1.5 mil base film; 1200' reels LP 35 = long play for 35-micron tape with 1.0 mil base film; 3600'/1800' reels DP 26 = double play for 26-micron tape with 0.75 mil base film; 2400' 7" reels TP 18 = triple play for 18-micron C-60 cassette tape; 15,000' pancakes QP 12 = quadruple play for 12-micron C-90 cassette tape; 23,700' pancakes XP 9 = extreme play for 9-micron C-120 cassette tape; 10,800' pancakes </pre> "LH" stood for "low noise, high output" oxide used for better than average performance. "LHL" was a formulation for low printthrough, and "LHS" was an advanced oxide with slightly higher coercivity intended for consumer use at slower 3.75/7.5 ips recordings rather than the more common 15 ips speeds used in the studios. So the SPR50 LHL from the late 1970s was a 1.5 mil backcoated studio tape with lower printthrough than normal. For the US, the names differed a bit: <pre>Performance = 3600'/1800' reels of LP35 standard oxide Studio = 3600'/1800' reels of LP35 LHS for slower consumer speeds Professional = 3600'/1800' of backcoated LPR35 LH for professional use </pre> In the mid 1980s, it was "clear" to the marketing departments that open-reel was dead as a consumer product. In the US, the product managers tossed out scores of unopened boxes of open reel tape into a dumpster. I climbed in and rescued them all for preservation and my own use. The professional group continued to sell the product, of course, and the naming conventions changed to distinguish the use of the product. <pre> LM 920 Loop Master chrome tape in 1- and half-inch width for loop bins LM 921 Loop Master bin tape with an improved formulation SM 910 Studio Master tape in widths from quarter inch to 2 inch; 50 microns SM 911 Studio Master tape with reduced modulation noise that replaced 910 SM 468 Studio Master tape inherited from Agfa; very high coercivity SM 900 Studio Master tape to compete with Ampex 499 and 3M 996 LPR 35 a throw back to the old naming convention for 1 mil tape </pre> It should be noted that BASF, unlike Agfa, Ampex, and 3M, never used the polyurethane infamous for breaking down over time and causing sticky tapes. I've used a lot of open reel tape over the years, and there is no other tape that outperforms BASF mechanically. Maxell made a great open reel tape; but in published, independent comparison tests for electro-acoustic properties of consumer open reel tapes, BASF was the regular winner. All of the tapes I salvaged years ago still wind perfectly with no significant rub off and no sign of shedding. The story I heard was that our chemical group refused to use the questionable polyurethane binder, not because of environmental concerns about longevity, but because Agfa-Gevaert held a license for it. They refused to pay Agfa for anything. That's why PEM 469 and 469 had shedding problems and SM 468 and SM 911 / LPR 35 LH(S) did not. If you're not having a problem with the sample you have and all of the others come from the same lot, then you may have product that Agfa produced with a different binder. They caught on quickly to the breakdown and were one of the first to promote the heat treatment for temporary salvage. I'd keep the tape and watch it closely for awhile. If no problems show up, you've got a great tape. After we bought Agfa, I wanted to stay with PEM 469 because it was already in use in some studios. The problem was that Agfa had a very small market share compared to Ampex and 3M, and PEM 469 had a reputation sullied by the binder breakdown. We decided to bring in SM 911 and 900 instead and price it slightly below Ampex and 3M. That was the biggest mistake of my career at BASF. No one was interested. Fortunately, no one noticed either. So I changed my mind and raise the price 15% above Ampex and 3M. That's when the studios got curious. (A "cheap" European tape is not interesting; but an expensive Porsche/Mercedes/BMW/Audio image is intriguing--especially when the client, not the studio, pays for the tape.) That's when sales really began to increase. Once 3M dropped out, we had the future wide open--until BASF sold the tape division off and fired all the experienced people. =cassette tape info= A data sheet for a tape has almost all the explanations of tape differences. However, they are hard to understand because of all the curves. Tape experts can judge a tape's electro-acoustic performance from a data sheet and estimate what it will sound like on a machine calibrated for a different tape and know what adjustments need to be made in order to align a deck to the tape described on the data sheet. The only quality parameters not mentioned on a data sheet are mechanical ones: rub-off, adhesion to the base film, stiction, surface polish, and so forth. (If I ever get time, I'll finish the paper on how to read a data sheet.) 1) Frequency response curve--although data sheets are full of curves, those curves represent the effect that bias current has on the output of number of signals at different frequencies. None of the curves is flat. If the sheet shows that a sweep of 12.5 kHz is 6 dB below the output for 315 Hz at -20 dB below the reference level, then the record pre-emphasis must be boosted by 6 dB at 12.5 kHz in order for "flat" response. I have nver seen the type of frequency response curve familiar to consumers on a tape data sheet because that type of curve is reliant on the hardware. 2) MOL is a very important characteristic, but it is offset by noise. Metal tapes have very high MOL values, but they also have poor noise levels. Their signal-to-noise ratios are often little or no better than those for high performance Type II tapes with lower MOL values and lower noise. MOL is a function of magnetic pigment, coating thickness, loading values (ratio of pigment to binder), and uniformity of particles and alignment. The values given in remanence figures correspond to MOL. 3) SOL defines short wavelength output at the point where an increase in input level no longer produces any increase in output because the tape saturates, that is, the high signal level begins to erase the output. This point is hard to define, so greater precision is given when two tones having a frequency difference of 6% are recorded simultaneously and the intermodulation between the two reaches 26.6 dB. SOL values are largely dependent on coercivity. The harder it is to coerce or force a particle to switch its magnetic poles, the harder it is for the particle to self-erase. Type IV metal tapes have the highest coercivity and, therefore, the highest SOL values for cassette tapes. For open-reel tape, SOL is less critical because the higher tape speeds increase the room for wavelengths and dramatically reduce the effect of self-erasure. However, note that "consumer" tapes often show slightly higher values of coercivity because they are designed for acceptable performance at 3.75 and 7.5 ips rather than the studio speeds of 15 or 30 ips. 4) Noise--there are several different measures of noise. Bias noise (a function of particle uniformity and alignment), modulation noise (a function of uniformity of dispersion within a coating, particle uniformity, and surface smoothness), and DC noise (particle shape and distribution). These noises depend on the tape design and processing far more than on any hardware. Chromium dioxide tapes are the best for all of these types of noise because the particle is a "perfect" shape--a long, thin glass-like rod with no external deformities. The shape makes the pigment easy to disperse and align in a coating and gives chrome the low noise values it has. Metal particles, although extremely small and nicely shaped, are very difficult to align because of their enormous coercivity. Coercivity gives metal tape the highest SOL values and excellent MOL values, but those values are reduced by the very high noise levels. For standard oxides, lower noise is a function of the pigment processing to reduce deformities of the particles (often called "dendrites"--Greek for "tree" because the uniformities look like branches coming from a tree trunk) and of the milling process to isolate and evenly disperse the particles within the coating. Ions of cobalt can be added to some standard oxide particles to raise their coercivity at the risk of some instability unless processing steps are taken to reduce the risk of lost remanence from physical forces (the magnetostrictive effect). 5) Uniformity is critical for tape, but what you described is a function of physical stability within a cassette housing, which brings up all sorts of other issue. Tape uniformity can mean two things: A) no deviation from batch to batch; and B) no deviation from beginning to end or from width to width. BASF held very tight specifications for batches of tape so that sensitivity at 315 Hz, for example, did not vary more than +/- 0.5 dB and for 10 kHz more than +/- 1.0 dB for millions of kilometers of duplication tape. This was because duplicators did not want to have to realign equipment for every batch that was delivered for their music cassettes. The beginning of a 23,000-ft cassette pancake should have exactly the same values at the end of the pancake so that the first cassette from the roll should sound exactly like the last cassette. In studio production, it was even more critical because the sensitivity across a 2-inch width of tape should not vary at all because multiple tracks had to remain in balance. BASF used a knife coating method, and the knife was controlled by a computer that sensed output of the coating and automatically adjusted thickness for uniformity of output. The values of thickness could change slightly through a reel or pancake, but the sensitivity did not. (I believe that Ampex and 3M also used the knife method while the Japanese used gravure coating. Stories about Nakamichi selecting only "center cuts" from TDK production may indicate why BASF/Agfa, Ampex, and 3M produced 1-inch and 2-inch mastering tapes and not the Japanese. There was a very distinct difference between tapes not only in pigment but also in processing. Now that there are only a few producers making only a few types, the differences are fewer that they used to be. =the end= BASF AG tried to unload the tape division to RAKS, the Turkish company, in September, 1996; but there was a riot when German workers found out. The deal was called off. In October of the same year, BASF AG convinced Kohap, the Korean chemical company, that buying a magnetic tape company made good sense for vertical integration. The argument was that demand for VHS video tape would remain strong with continuing but slow growth until demand peaked in 2010--that's last year!--with a slow decline in subsequent years. The BASF management actually believed it and forced anyone with a different opinion to keep quiet. Kohap fell for it. Kohap arranged to keep the BASF logo for five years, with the "by EMTEC" qualification in place until such time that EMTEC would appear in the white rectangle in the logo. EMTEC was the subsidiary fully owned by Kohap, except in the United States where BASF management sold rights to distribute EMTEC products to Joseph Ryan (professional products, which was the only profitable division) and Sigmar Tullman (computer products). The reason for this odd approach was that the Department of Justice could not stop these "independent" distributors from their business if BASF were found guilty of price fixing for a third time. Kohap was not aware of this arrangement and was furious when they found out. In 1998 Kohap bought the professional and computer business back, but Mr. Ryan, who had named his company "JRPro Sales" after himself, had in six months brought the professional division to such losses that EMTEC could never recover. Korea fell into a severe recession a few years later, and Kohap was forced to sell off EMTEC to investment bankers. Once these bankers saw the books, they were appalled. It didn't take long for them to break the company apart and sell off whatever they could to anyone interested. Imation and Aurex bought some equipment and raw materials. Most of the rest went to scrap. BASF had an operation just across the German border in France where audio and video tapes were loaded into housings molded and assembled in the same plant. I don't know why these cassettes are labeled "Made in Korea" unless they are part of an arrangement with SKC. SKC, Aurex, and BASF were all engaged in price fixing bulk audio tape in 1994 and 1995, and there were meetings in Seoul, Korea even in early 1997. S.K. Moon from SKC attended the first meetings and was fired for refusing to attend any more. He sued SKC in the state of California, and that's when the U.S. Justice Department got wind of the arrangement. Two weeks after Moon sued SKC, BASF Magnetics announced the fire sale to Kohap and fired Terry O'Kelly, the only BASF director who refused to participate in any illegal meetings at all. Since Kohap had no tape production, loading, or packaging equipment at all in Korea, these cassettes are either from SKC or from Saehan, another supplier to BASF in those days. Even though there was a loading and packaging operation in France, if the cassettes say "Made in Korea," they would have to have come from either SKC or Saehan. The reason for the long story is that it had a lasting affect on tape production. In 1996 BASF Magnetics in the U.S. was expanding its professional division, and a number of Quantegy executives had asked O'Kelly if they could be part of that expansion. They all knew that VHS and audio cassettes had a limited life, but pro audio/video could be based on tape products if there were a reliable source. BASF had hired top sales people from Quantegy, Fuji, and Sony in the summer of 1996; and there was every reason to believe that BASF could easily become the largest and most stable tape supplier in the world. The threat of the price fixing lawsuit destroyed all that. BASF replaced O'Kelly with Ryan, the new sales people quit and sued BASF for "misrepresentation," and what was formerly the most profitable division began to bleed money. 3M had abandoned tape; Quantegy was struggling; and now BASF shot itself in the face. Recording studios watched all of this and decided that a move to digital was the safest bet. Analogue tape recording did not have to die off as quickly as it did. =sticky shed syndrome= The sticky-shed syndrome is a function of a breakdown in the polyurethane binder used for the magnetic coating due to hydrolysis--allowing water molecules to attach themselves to the magnetic pigment. The "baking" method merely drives the water molecules out of the coating for a temporary fix. Repeated bakings are less effective because the heat itself may stress the coating chemistry. The only association with backcoating that I am aware of is coincidence--the binder used was expensive and used almost entirely on premium tapes that were always backcoated. The problem is the oxide coating, not the backcoating. Calendering is a process of using rollers filled with either hot or cold water or oil--the choices varied depending on the type of coating--that squeeze the magnetic surface of the magnetic coating to flatten and polish it. Backcoating is applied after calendering because the surface of the backcoat must be rough enough to allow air to pass across its surface in order to provide smooth winds at high speeds. I don't know enough about molecular chemistry to offer any expert opinion about the effectiveness of using NuFinish to resolve the problem, but I do know that surface finishes were applied to some tapes after coating and calendering for specific applications. The composition of NuFinish is designed to add a quick-drying lubricant to the surface of paint and to use micro- or nano-particles to fill in scratches so that the paint surface looks smooth. Magnetic tape is little more than magnetic paint on plastic film. In fact, the first tapes were reddish brown because the ferric oxide used was very similar to that used in inexpensive paints. Barns are red or reddish-brown because the color pigment used in those paints is iron oxide--cheap, stable (it's already rusted!), and effective. Applying a paint finish to a magnetic tape is not that far off the mark. Those who have tried it claim that it allows tapes formerly cursed with the binder breakdown to not only run without sticking but to be able to reproduce themselves effectively, even after long periods of time. That would be significant. If that works predictably for every binder-failed tape that needs to be transferred to another medium, it would be a better solution than baking a tape. However, if the treated tape is to be kept as a master, then one must investigate some other considerations: 1) does the treatment work for all the various binders that have failed (Ampex, Agfa, 3M); 2) does the treatment last for all the various binders; 3) does the treatment lead to any other deterioration; 4) does the treatment have any effect on headwear; 5) does the treatment have an effect on gap life? Micro- and nano-particle technology have come a long way since tapes have been manufactured, as has polymer technology. It would not be a surprise to me that developments meant for auto paint finishes would also work for magnetic paint finishes. It's a pity BASF got out of tape so soon because they are also a very large auto paint supplier. ---- The code works this way: <pre> SP50/52 = single play on 1.5-mil base film; total thickness from 48-50 microns LP35 = long play on 1.0-mil base film; total thickness from 35-36 microns DP26 = double play on .75-mil base film; total thickness 26-29 microns TP18 = triple play for cassette C-60 tape or super-thin open-reel QP12 = quadruple play for cassette C-90 tape XP9 = extended play for cassette C-120 tape </pre> For reels, the lengths are:<pre> 7-inch reel 10.5-inch reel 1200 feet 2400 feet SP50 1800 feet 3600 feet LP35 2400 feet DP26 3600 feet TP18 </pre> If there is an "R" after the length designation, the tape is backcoated. The next two or three digits designate the type of coating. "SPR50 LHL" was a studio tape on 1.5-mil film with a total coating thickness of 52 microns, including the backcoating. The oxide was Low noise, High output, with Low print levels. The gray cases or black cases were used for a number of different "domestic" or consumer open-reel products. SP52 was a "general purpose" tape with average performance. Although LP35 LH and LPR35 LH would seem to differ only in the backcoating, they used different manufacturing processes so that the former was an average tape while the backcoated version was a much higher performance tape suited for 7.5 or 15 ips recording. LHS tape had a higher coercivity designed for good performance at 3.75 or 7.5 ips recording speeds. Over the years oxides and processes changed more often than the names, so it is sometimes hard to equate performance with just a name. Although BASF did not suffer from binder breakdown, the standard LH formulation--called "Performance" in the U.S.--did have some slight granular rub-off of the oxide. LPR35 and LP35 LHS were as clean as a whistle--I have never found oxide on guides or heads when using those tapes. =Ampex and SSS= Unlike Ampex, who used polyurethane in their binder mix, when the SSS issue came to light in the early 1990s, in a meeting (organised by Ampex BTW) between the tape manufacturers and the ARP, BASF stated they only ever used polyethylene in their binder and their tests showed it did not suffer from hydrolysis. This tape may be suffering from other break down cased by poor storage. It’s likely to be heading for 40+ years old as it is. The boxes may look ok but if the RH of the storage area is too low or it’s subject to extremes of dry heat or cold, that could affect it. BTW Ampex made more 456 than any other tape from any other manufacturer by a long margin and for a long time. Over that period they bought binder in from a number of suppliers, 3M being one. The issue that causes SSS is hydrolysis. All PE binder suffers from this but the “string length” of the PE strands dictate how quickly this occurs. Test made on short string PE showed it could suffer from hydrolysis within 48 hours. But long stringed PE binder was inconsistent in its coating of the backing making the tape surface bumpy. Medium string was the compromise. But until Ampex installed gas spectroscopy equipment in their production plants in 1981 to check the consistency of string length, the previous binder mixes they used had a variable mixture of string lengths. Hence not all 456 suffers extreme SSS, but due to the late introduction of the GS inspection kit in the manufacturing lifespan of the product, the chance that Ampex products do suffer SSS is likely. Coupled to this is storage conditions: The ideal temp and RH, both or which, the tape manufacturers recognised that the users of their products were very unlikely to have in their tape stores. And you thought reel to reel was just a bit of rust moving over a bit of metal to make a sound! 8b36e209155e2372fa36ef15f8f940e9d3bb64eb 0 614 2768 2024-03-29T18:17:58Z Pvdm 2 Created page with "IMPORTANT FOR VST INSTALLATIONS: If you deploy plugins as a subdirectory of your VST2 directory, the subdirectory should contain substring 'lsp-plugins'. Otherwise plugins won't find the VST2 core library. Please notice that '~' means user's home directory. ## For Linux/FreeBSD The usual directories for LADSPA are: * /usr/lib/ladspa * /usr/local/lib/ladspa * /usr/lib64/ladspa * /usr/local/lib64/ladspa * ~/.ladspa The usual directories for LV2 are: * /usr..." wikitext text/x-wiki IMPORTANT FOR VST INSTALLATIONS: If you deploy plugins as a subdirectory of your VST2 directory, the subdirectory should contain substring 'lsp-plugins'. Otherwise plugins won't find the VST2 core library. Please notice that '~' means user's home directory. ## For Linux/FreeBSD The usual directories for LADSPA are: * /usr/lib/ladspa * /usr/local/lib/ladspa * /usr/lib64/ladspa * /usr/local/lib64/ladspa * ~/.ladspa The usual directories for LV2 are: * /usr/lib/lv2 * /usr/local/lib/lv2 * /usr/lib64/lv2 * /usr/local/lib64/lv2 * ~/.lv2 The usual directories for LinuxVST are: * /usr/lib/vst * /usr/local/lib/vst * /usr/lib64/vst * /usr/local/lib64/vst * ~/.lxvst * ~/.vst The usual directories for JACK core library are: * /usr/lib * /usr/local/lib * /lib * /usr/lib64 * /usr/local/lib64 * /lib64 The usual directories for JACK binaries are: * /usr/bin * /usr/local/bin * /bin * /usr/sbin * /usr/local/sbin * /sbin The usual directories for CLAP are: * /usr/lib/clap * /usr/local/lib/clap * /usr/lib64/clap * /usr/local/lib64/clap * ~/.clap ec3d527386eb62eb37e87a43b7bdcc591320a21d 0 501 2773 2772 2024-04-04T08:15:23Z Pvdm 2 /* Compatibility */ wikitext text/x-wiki =NAB= The NAB eq curve, used in North America, employs time constants of '''3183 usec (50 Hz)''' for the bass, & '''50 usec (3183 Hz)''' for the treble, at speeds of 7.5 & 15 ips, in playback mode. This spec originated in the early 1950's, when tapes had less HF capability, & bass boost in recording was employed at 50 Hz to avoid LF rumble during playback. =IEC= The IEC curve came a little later and is a curve which better matches and better utilizes the benefits of improved tapes. It uses an '''infinite''' time constant in the bass end (0 Hz), and a '''35 µsec (4547 Hz)''' time constant in the treble region at 15 IPS speed. At 7.5 IPS, bass is the same, but the treble time constant is '''70 µsec (2274 Hz)'''. Again, IEC EQ provides less treble boost in playback (at 15 IPS speed), realizing a slight improvement in S/N ratio over NAB EQ. The difference is about <u>1.0</u> to <u>1.5 dB</u>. At 7.5 IPS speed, NAB provides less treble boost and a little better S/N, <u>1.0 to 1.5 dB</u>. =Compatibility= A tape recorded at 15 IPS w/ NAB EQ & played back w/ IEC EQ, will likely sound a little deficient in the treble, as well as in the deep bass. But the amount is not that great, like a dB or so. A tape recorded in IEC, then played back in NAB will have slightly boosted treble & bass. The freq response is not flat this way, but there will always be some listeners who prefer boosted sound at the bass & treble regions. If the recording speed was 7.5 IPS, then IEC provides more playback treble boost than NAB. So the treble response will vary in the opposite direction as above, but still a small difference. Bass remains the same as above. If "flat" is the objective, then it is recommend to play back with the same EQ curve used during recording. Still, the difference is pretty slim, and if the right curve is not available, a parametric or graphic outboard EQ can restore flat response. Use the break frequencies given above and all should be well. Again, if an outboard EQ is not available either, no big deal. The deviation from flat response is too scant to be concerned about. 2257d678f3ace612c00d6a9d8fe1d7dd5471adca 0 97 2774 2667 2024-05-13T19:31:40Z Pvdm 2 wikitext text/x-wiki *[[envy]] *[[hupsie]] *[[lesie]] *[[usb wifi dongles]] *[[usb drives]] *[[glmark2 benchmark]] *[[tecra]] *[[wifi VUmc]] *[[lapx]] *[[lap088]] *[[sheba]] *[[amd64]] *[[Dell Latitude D610 DCC-Studio]] *[[akoya]] *[[zbox]] *[[hpspil]] *[[webcams]] *[[cpu3972]] *[[samsie]] *[[WeTab]] *[[nw nb]] *[[asus f2a85-v]] *[[asus P5Q Pro]] *[[edup]] *[[aida screen]] 21fe231fce872bb4407dce0af73b0f14a5343204 0 615 2778 2777 2024-05-13T19:32:55Z Pvdm 2 wikitext text/x-wiki *[[partitions-hupsie]] f32fe140c97f66469f9711652742665a6c88d89b 0 616 2780 2779 2024-05-14T08:16:24Z Pvdm 2 wikitext text/x-wiki hd0 476GB * P1 260MB EFI * P2 16MB MS RESERVED * P3 134GB win * P5 100GB / * P6 120GB /home * P7 100GB /data * P8 16GB swap * 659MB herstelpartitie e8c69e3703ac444b17c1e644aff701005d85f290 0 72 2784 2254 2024-06-27T18:20:28Z Pvdm 2 wikitext text/x-wiki *[[Upgrade using patch]] *[[installation MediaWiki]] *[[Backup MediaWiki]] *[[Upgrading to mediawiki 1.18]] *[[File permissions]] c6e097ee49d6c4b42413136fba9bc8e986e3f10b 0 617 2786 2785 2024-06-27T18:25:38Z Pvdm 2 wikitext text/x-wiki === Using patch === <!--T:63--> A small patch file is usually made available for a minor version upgrade. You'll need to download [[w:patch (Unix)|patch]] to use this Manually download and extract the patch file from [https://releases.wikimedia.org/mediawiki/ the dumps site] or follow the directions with wget below. Patches are incremental, you can '''not ''' skip a version. # <kbd>cd</kbd> to your main MediaWiki directory (the one with LocalSettings.php) # Download the patch file and <kbd>unzip</kbd> it. # Use <code>patch -p1 --dry-run</code> to check what will be changed (''e.g.'', <code>patch -p1 --dry-run -i ''mediawiki-x.xx.x.patch''</code>) # If all is well, run <kbd>patch</kbd> again without <code>--dry-run</code> # Check your Special:Version and you should see the new version number in place. 622b2ba7e5c179d6edf5423433bce27a2155b491 0 618 2789 2024-07-11T10:01:50Z Pvdm 2 Created page with "To download video with english subtitles: # yt-dlp --write-sub --sub-lang "en.*" {URL} This downloads all variants of the english language" wikitext text/x-wiki To download video with english subtitles: # yt-dlp --write-sub --sub-lang "en.*" {URL} This downloads all variants of the english language 18b15653f8435a6e18b5d5cdade81c45e5eefd7a 0 619 2791 2024-07-11T10:03:20Z Pvdm 2 Created page with "*[[Use yt-dlp with subtitles for video files]] *[[Use yt-dlp the correct way for music files]]" wikitext text/x-wiki *[[Use yt-dlp with subtitles for video files]] *[[Use yt-dlp the correct way for music files]] 339500413aa651abc3112b0e90b910f67058ab6c 0 620 2795 2794 2024-07-12T09:27:09Z Pvdm 2 wikitext text/x-wiki When the PC will not boot from USB, you can use GRUB2 to boot from the USB. In the GRUB menu: Press 'c' to go the GRUB prompt grub> ls (hd0) (hd0,msdos1) ... grub> set root=hd0,msdos1 grub> chainloader /efi/boot/bootx64.efi grub> boot The USB boot menu will appear. The above is of course an example, every situation will be different. But the idea is the same. ff1e0c08365ddaf99451588411d66987451559df 0 611 2800 2781 2024-07-25T17:08:23Z Pvdm 2 wikitext text/x-wiki Use: -f bestaudio -f ba --extract-audio --audio-format flac for best audio quality. -o "%(title)s.%(ext)s" for correct naming of the files. --add-metadata for correct IDs. --parse-metadata "playlist_index:%(track_number)s" for parsing track numbers. --embed-thumbnail This instructs yt-dlp to embed the thumbnail image in the downloaded audio file. You can use youtube URLS to download complete album in one go: #yt-dlp -f bestaudio -o "%(title)s.%(ext)s" --add-metadata --parse-metadata "playlist_index:%(track_number)s" https://www.youtube.com/playlist?list=OLAK5uy_nBJgNLqUL8A64tQMKFNPK3x7KzNOgfbUw =Embed thumbnail in opus music files= #ffmpeg -i audio_file.opus -i thumbnail.jpg -c:v mjpeg -c:a copy -metadata:s:v title="Album Art" output_file.opus b66f231a9d79050d834a3b0618c126c5ef19f079 0 139 2802 2801 2024-07-25T19:23:53Z Pvdm 2 /* normalize to LUFS standard */ wikitext text/x-wiki =NORMALIZE= # zypper in normalize SYNOPSIS normalize [ options ] [ -- ] file ... First, make a copy of the file. Then do one of the following: # normalize test.wav normalizes at -15 dB ??? # normalize -a Adjust the RMS volume to the target amplitude AMPLITUDE; must be between 0.0 and 1.0. If a number suffixed by "dB" or "dBFS" is specified, the amplitude is assumed to be in decibels from full scale. The default is -12dBFS. # normalize -b BATCH MODE '''When operating on a group of unrelated files, you usually want all of them at the same level, and this is the default behavior. However, a group of music files all from the same album is generally meant to be listened to at the relative volumes they were recorded at. In batch mode, all the specified files are considered to be part of a single album and their relative volumes are preserved. This is done by averaging the volumes of all the files, computing a single adjustment from that, and applying the same adjustment to all the files. Some analysis is also done so that files with volumes that appear to be statistical aberrations are not considered in the average. This is useful if you have albums (like many of the author's) in which there is one "quiet song" that throws off the average. ''' # normalize -m, --mix Enable mix mode: see MIX MODE, below. Batch mode and mix mode are mutually exclusive. '''This mode is made especially for making mixed CD's and the like. You want every song on the mix to be the same volume, but it doesn't matter if they are the same volume as the songs on some other mix you made last week. In mix mode, average level of all the files is computed, and each file is separately normalized to this average volume.''' # normalize -n '''Compute and output the volume adjustment that would set the volume to the target, but don't apply it to any of the files (i.e. skip the second phase). If you use this option, your files will not be altered in any way. ''' # normalize --peak Adjust using peak levels instead of RMS levels. Each file will be adjusted so that its maximum sample is at full scale. This just gives a file the maximum volume possible without clipping; no normalization is done. # normalize -v Increase verbosity. This option can be repeated for more messages. -- end of options =FFMPEG= ==Detect RMS level== # ffmpeg -i inputfile.flac -filter:A volumedetect -f null /dev/null ... [Parsed_volumedetect_0 @ 0x562a0076b200] n_samples: 23664648 '''[Parsed_volumedetect_0 @ 0x562a0076b200] mean_volume: -12.6 dB''' [Parsed_volumedetect_0 @ 0x562a0076b200] max_volume: 0.0 dB [Parsed_volumedetect_0 @ 0x562a0076b200] histogram_0db: 24907 </pre> eventueel: # for i in *; do ffmpeg -i "$i" -filter:a volumedetect -f null /dev/null 2>&1 | grep mean; done ==normalize to LUFS standard== # ffmpeg -i videofile.mp4 -af loudnorm=I=-24:LRA=11:TP=-1 -b:a 160k output-lufs.mp3 # for i in *; do ffmpeg -i "$i" -af loudnorm=I=-24:LRA=11:TP=-1 -b:a 160k "$i"-lufs.mp3; done where I = integrated loudness LRA = loudness range TP = true peak ===to normalize audio from mp4 video files in parallel=== # ls -U *.mp4 | parallel -j6 ffmpeg -i {} -af loudnorm=I=-24:LRA=11:TP=-1 -b:a 160k {/.}-lufs.mp3 Tune the parameter j6 to your #cores. This is faster than -threads 0 parameter, which is supposed to use all cores but doesn't. =SOX= # sox inputfile.flac -n stat # sox inputfile.flac -n stats Overall Left Right DC offset 0.000638 0.000397 0.000638 Min level -0.773560 -0.773560 -0.773560 Max level 0.773529 0.773529 0.773529 Pk lev dB -2.23 -2.23 -2.23 '''RMS lev dB -14.84 -15.28 -14.43''' RMS Pk dB -8.71 -10.03 -8.71 RMS Tr dB -inf -inf -inf Crest factor - 4.49 4.07 Flat factor 1.74 2.13 1.58 Pk count 131 72 190 Bit-depth 16/16 16/16 16/16 Num samples 11.8M Length s 268.307 Scale max 1.000000 Window s 0.050 5603ef82c60c4f021b9af48d11272af88152b89a 0 552 2803 2712 2024-08-26T16:41:29Z Pvdm 2 wikitext text/x-wiki To check settings =Which sound cards are installed, and what number are they?= > cat /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xfc080000 irq 69 1 [Generic ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfc500000 irq 72 2 [USB ]: USB-Audio - Scarlett 2i2 USB Focusrite Scarlett 2i2 USB at usb-0000:30:00.4-2.3, high speed 3 [Pro ]: USB-Audio - FiiO K5 Pro GuangZhou FiiO Electronics Co.,Ltd FiiO K5 Pro at usb-0000:30:00.4-1, high spee =Focusrite Scarlett 2i2= <pre> > cat /proc/asound/card2/stream0 Focusrite Scarlett 2i2 USB at usb-0000:30:00.4-2.3, high speed : USB Audio Playback: Status: Stop Interface 1 Altset 1 Format: S32_LE Channels: 2 Endpoint: 0x01 (1 OUT) (SYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000 Data packet interval: 125 us Bits: 24 Channel map: FL FR Capture: Status: Running Interface = 2 Altset = 1 Packet Size = 200 Momentary freq = 192000 Hz (0x18.0000) Interface 2 Altset 1 Format: S32_LE Channels: 2 Endpoint: 0x82 (2 IN) (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000 Data packet interval: 125 us Bits: 24 Channel map: FL FR </pre> =UCA202:= # cat /proc/asound/CODEC/pcm0p/sub0/hw_params # cat /proc/asound/card0/codec#0 <pre> access: MMAP_INTERLEAVED format: S16_LE subformat: STD channels: 2 <-------- will be 4 for iO4 rate: 48000 (48000/1) <------ this changes with the input audio file period_size: 44100 buffer_size: 88200 </pre> =FiiO= 48kHz and below: BLUE 48kHz and above: YELLOW DSD: GREEN # cat /proc/asound/card0/stream0 | grep Momentary or # cat /proc/asound/card1/stream0 | grep Momentary <pre> Momentary freq = 44095 Hz (0x5.8308) </pre> - - - - # cat /proc/asound/card0/stream0 # cat /proc/asound/card0/pcm0p/sub0/hw_params <pre> GuangZhou FiiO Electronics Co.,Ltd FiiO K5 Pro at usb-0000:00:12.2-3, high spee : USB Audio Playback: Status: Running Interface = 1 Altset = 2 Packet Size = 36 Momentary freq = 44095 Hz (0x5.8308) Feedback Format = 16.16 Interface 1 Altset 1 Format: S32_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000 Data packet interval: 125 us Interface 1 Altset 2 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000 Data packet interval: 125 us Interface 1 Altset 3 Format: SPECIAL Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000 Data packet interval: 125 us </pre> =FiiO via S/PDIF= # cat /proc/asound/card1/pcm1p/sub0/hw_params <pre> access: MMAP_INTERLEAVED format: S32_LE subformat: STD channels: 2 rate: 48000 (48000/1) period_size: 1024 buffer_size: 32768 </pre> 7bc6d446ad17aacbf9a00db333f264e06c7d7043 0 621 2819 2818 2025-01-25T19:11:42Z Pvdm 2 /* To enable wifi after resume, when it is turned off */ wikitext text/x-wiki =To enable wifi after resume, when it is turned off= Create a systemd service “root-resume.service” in /etc/systemd/system with content: <pre> [Unit] Description=Local system resume actions After=suspend.target [Service] Type=simple ExecStart=/usr/bin/nmcli radio wifi on [Install] WantedBy=suspend.target </pre> and enable the newly created service: # systemctl enable root-resume.service 1841cf795f564d9e1398feb4f347ee8532a14a4d 0 541 2820 2211 2025-02-07T10:41:42Z Pvdm 2 wikitext text/x-wiki = Bash Pitfalls = This page shows common errors that Bash programmers make. These examples are all flawed in some way. You will save yourself from many of these pitfalls if you simply '''[[Quotes|always use quotes]]''' and never use WordSplitting for any reason! Word splitting is a broken legacy misfeature inherited from the Bourne shell that's stuck on by default if you don't quote expansions. The vast majority of pitfalls are in some way related to unquoted expansions, and the ensuing word splitting and globbing that result. <<TableOfContents>> <<Anchor(pf1)>> == for f in $(ls *.mp3) == One of the most common mistakes [[BASH]] programmers make is to write a loop like this: <pre> for f in $(ls *.mp3); do # Wrong! some command $i # Wrong! done for f in $(ls) # Wrong! for f in `ls` # Wrong! for f in $(find . -type f) # Wrong! for f in `find . -type f` # Wrong! files=($(find . -type f)) # Wrong! for f in ${files[@]} # Wrong! </pre> Yes, it would be great if you could just treat the output of `ls` or `find` as a list of filenames and iterate over it. But you '''cannot'''. This entire approach is fatally flawed, and there is no trick that can make it work. You must use an entirely different approach. There are at least 6 problems with this: * If a filename contains whitespace, it undergoes WordSplitting. Assuming we have a file named `01 - Don't Eat the Yellow Snow.mp3` in the current directory, the `for` loop will iterate over each word in the resulting file name: ''01'', ''-'', ''Don't'', ''Eat'', etc. * If a filename contains [[glob]] characters, it undergoes filename expansion ("[[glob|globbing]]"). If `ls` produces any output containing a '''*''' character, the word containing it will become recognized as a pattern and substituted with a list of all filenames that match it. * If the command substitution returns multiple filenames, there is no way to tell where the first one ends and the second one begins. Pathnames may contain ''any'' character except NUL. Yes, this includes newlines. * The `ls` utility may mangle filenames. Depending on which platform you're on, which arguments you used (or didn't use), and whether its standard output is pointing to a terminal or not, `ls` may randomly decide to replace certain characters in a filename with "?", or simply not print them at all. [[ParsingLs|Never try to parse the output of ls]]. `ls` is just plain unnecessary. It's an external command whose output is intended specifically to be read by a human, not parsed by a script. * The CommandSubstitution strips ''all'' trailing newline characters from its output. That may seem desirable since `ls` adds a newline, but if the last filename in the list ends with a newline, <pre>`...`</pre> or `$()` will remove ''that'' one also. * In the `ls` examples, if the first filename starts with a hyphen, it may lead to [[#pf3|pitfall #3]]. You can't simply double-quote the substitution either: <pre> for f in "$(ls *.mp3)"; do # Wrong! </pre> This causes the entire output of `ls` to be treated as a single word. Instead of iterating over each file name, the loop will only execute ''once'', assigning to `f` a string with all the filenames rammed together. Nor can you simply change [[IFS]] to a newline. Filenames can also contain newlines. Another variation on this theme is abusing word splitting and a `for` loop to (incorrectly) read lines of a file. For example: <pre> IFS=$'\n' for line in $(cat file); do ... # Wrong! </pre> [[DontReadLinesWithFor|This doesn't work]]! Especially if those lines are filenames. Bash (or any other Bourne family shell) just doesn't work this way. '''So, what's the right way to do it?''' There are several ways, primarily depending on whether you need a recursive expansion or not. If you don't need recursion, you can use a simple [[glob]]. Instead of `ls`: <pre> for file in ./*.mp3; do # Better! and... some command "$file" # ...always double-quote expansions! done </pre> POSIX shells such as Bash have the globbing feature specifically for this purpose -- to allow the shell to expand patterns into a list of matching filenames. There is no need to interpret the results of an external utility. Because globbing is the very last expansion step, each match of the `./*.mp3` pattern correctly expands to a separate word, and isn't subject to the effects of an unquoted expansion. ''Question:'' What happens if there are no *.mp3-files in the current directory? Then the for loop is executed once, with i="./*.mp3", which is not the expected behavior! The workaround is to test whether there is a matching file: <pre> # POSIX for file in ./*.mp3; do [ -e "$file" ] || continue some command "$file" done </pre> Another solution is to use Bash's `shopt -s nullglob` feature, though this should only be done after reading the documentation and carefully considering the effect of this setting on all other globs in the script. If you need recursion, the standard solution is `find`. When [[UsingFind|using find]], be sure you use it properly. For POSIX sh portability, use the `-exec` option: <pre> find . -type f -name '*.mp3' -exec some command {} \; # Or, if the command accepts multiple input filenames: find . -type f -name '*.mp3' -exec some command {} + </pre> If you're using bash, then you have two additional options. One is to use GNU or BSD `find`'s `-print0` option, together with bash's `read -d ''` option and a ProcessSubstitution: <pre> while IFS= read -r -d '' file; do some command "$file" done < <(find . -type f -name '*.mp3' -print0) </pre> The advantage here is that "some command" (indeed, the entire `while` loop body) is executed in the current shell. You can set variables and have them [[BashFAQ/024|persist after the loop ends]]. The other option, available in [[BashFAQ/061|Bash 4.0 and higher]], is `globstar`, which permits a glob to be expanded recursively: <pre> shopt -s globstar for file in ./**/*.mp3; do some command "$file" done </pre> Note the double quotes around `$file` in the examples above. This leads to our second pitfall: <<Anchor(pf2)>> == cp $file $target == What's wrong with the command shown above? Well, nothing, '''if''' you happen to know in advance that `$file` and `$target` have no white space or [[glob|wildcards]] in them. However, the results of the expansions are still subject to WordSplitting and [[glob|pathname expansion]]. Always double-quote parameter expansions. <pre> cp -- "$file" "$target" </pre> Without the double quotes, you'll get a command like `cp 01 - Don't Eat the Yellow Snow.mp3 /mnt/usb`, which will result in errors like <pre>cp: cannot stat `01': No such file or directory</pre>. If `$file` has wildcards in it ('''*''' or '''?''' or '''['''), they will be [[glob|expanded]] if there are files that match them. With the double quotes, all's well, unless "$file" happens to start with a `-`, in which case `cp` thinks you're trying to feed it command line options (See [[#pf3|pitfall #3]] below.) Even in the somewhat uncommon circumstance that you can guarantee the variable contents, it is conventional and good practice to [[Quotes|quote]] parameter expansions, especially if they contain file names. Experienced script writers will always use [[Quotes|quotes]] except perhaps for a small number of cases in which it is ''absolutely'' obvious from the immediate code context that a parameter contains a guaranteed safe value. Experts will most likely consider the `cp` command in the title always wrong. You should too. <<Anchor(pf3)>> == Filenames with leading dashes == Filenames with leading dashes can cause many problems. Globs like `*.mp3` are sorted into an expanded list (according to your current [[locale]]), and `-` sorts before letters in most locales. The list is then passed to some command, which may incorrectly interpret the `-filename` as an option. There are two major solutions to this. One solution is to insert `--` between the command (like `cp`) and its arguments. That tells it to stop scanning for options, and all is well: <pre> cp -- "$file" "$target" </pre> There are potential problems with this approach. You have to be sure to insert `--` for ''every'' usage of the parameter in a context where it might possibly be interpreted as an option -- which is easy to miss and may involve a lot of redundancy. Most well-written option parsing libraries understand this, and the programs that use them correctly should inherit that feature for free. However, still be aware that it is ultimately up to the application to recognize ''end of options''. Some programs that manually parse options, or do it incorrectly, or use poor 3rd-party libraries may not recognize it. Standard utilities ''should'', with a few exceptions that are specified by POSIX. `echo` is one example. Another option is to ensure that your filenames always begin with a directory by using relative or absolute pathnames. <pre> for i in ./*.mp3; do cp "$i" /target ... done </pre> In this case, even if we have a file whose name begins with `-`, the glob will ensure that the variable always contains something like `./-foo.mp3`, which is perfectly safe as far as `cp` is concerned. Finally, if you can guarantee that all results will have the same prefix, and are only using the variable a few times within a loop body, you can simply concatenate the prefix with the expansion. This gives a theoretical savings in generating and storing a few extra characters for each word. <pre> for i in *.mp3; do cp "./$i" /target ... done </pre> <<Anchor(pf4)>> == [ $foo = "bar" ] == This is very similar to the issue in pitfall #2, but I repeat it because it's ''so'' important. In the example above, the [[Quotes|quotes]] are in the wrong place. You do ''not'' need to quote a string literal in bash (unless it contains metacharacters or pattern characters). But you ''should'' quote your variables if you aren't sure whether they could contain white space or wildcards. This example can break for several reasons: * If a variable referenced in `[` doesn't exist, or is blank, then the `[` command would end up looking like: . <pre> [ = "bar" ] # Wrong! </pre> . ...and will throw the error: `unary operator expected`. (The `=` operator is ''binary'', not unary, so the `[` command is rather shocked to see it there.) * If the variable contains internal whitespace, then it gets [[WordSplitting|split into separate words]] before the `[` command sees it. Thus: . <pre> [ multiple words here = "bar" ] </pre> . While that may look OK to you, it's a syntax error as far as `[` is concerned. The correct way to write this is: . <pre> # POSIX [ "$foo" = bar ] # Right! </pre> . This works fine on POSIX-conformant implementations even if `$foo` begins with a `-`, because POSIX `[` determines its action depending on the number of arguments passed to it. Only very ancient shells have a problem with this, and you shouldn't worry about them when writing new code (see the `x"$foo"` workaround below). In Bash and many other ksh-like shells, there is a superior alternative which uses the [[BashFAQ/031|[[ keyword]]. <pre> # Bash / Ksh [[ $foo == bar ]] # Right! </pre> You don't need to quote variable references on the left-hand side of `=` in `[[ ]]` because they don't undergo word splitting or [[glob|globbing]], and even blank variables will be handled correctly. On the other hand, quoting them won't hurt anything either. Unlike `[` and `test`, you may also use the identical `==`. Do note however that comparisons using `[[` perform pattern matching against the string on the right hand side, not just a plain string comparison. To make the string on the right literal, you must quote it if any characters that have special meaning in pattern matching contexts are used. <pre> # Bash / Ksh match=b*r [[ $foo == "$match" ]] # Good! Unquoted would also match against the pattern b*r. </pre> You may have seen code like this: <pre> # POSIX / Bourne [ x"$foo" = xbar ] # Ok, but usually unnecessary. </pre> The `x"$foo"` hack is required for code that must run on ''very'' ancient shells which lack [[BashFAQ/031|[[]], and have a more primitive `[`, which gets confused if `$foo` begins with a `-`. On said older systems, `[` still doesn't care whether the token on the right hand side of the `=` begins with a `-`. It just uses it literally. It's just the left-hand side that needs extra caution. Note that shells that require this workaround are not POSIX-conforming. Even the Heirloom Bourne shell doesn't require this (probably the non-POSIX Bourne shell clone that's still most widely in use as a system shell). Such extreme portability is rarely a requirement and makes your code less readable (and uglier). <<Anchor(pf5)>> == cd $(dirname "$f") == This is yet another [[Quotes|quoting]] error. As with a variable expansion, the result of a CommandSubstitution undergoes WordSplitting and [[glob|pathname expansion]]. So you should quote it: <pre> cd -P -- "$(dirname -- "$f")" </pre> What's not obvious here is how the [[Quotes|quotes]] nest. A C programmer reading this would expect the first and second double-quotes to be grouped together; and then the third and fourth. But that's not the case in Bash. Bash treats the double-quotes ''inside'' the command substitution as one pair, and the double-quotes ''outside'' the substitution as another pair. Another way of writing this: the parser treats the command substitution as a "nesting level", and the quotes inside it are separate from the quotes outside it. <<Anchor(pf6)>> == [ "$foo" = bar && "$bar" = foo ] == You can't use `&&` inside the [[BashFAQ/031|old test (or [) command]]. The Bash parser sees `&&` outside of `[[ ]]` or `(( ))` and breaks your command into ''two'' commands, before and after the `&&`. Use one of these instead: <pre> [ bar = "$foo" ] && [ foo = "$bar" ] # Right! (POSIX) [[ $foo = bar && $bar = foo ]] # Also right! (Bash / Ksh) </pre> (Note that we reversed the constant and the variable inside `[` for the legacy reasons discussed in pitfall #4. We could also have reversed the `[[` case, but the expansions would require quoting to prevent interpretation as a pattern.) The same thing applies to `||`. Either use `[[` instead, or use two `[` commands. Avoid this: <pre> [ bar = "$foo" -a foo = "$bar" ] # Not portable. </pre> The binary `-a` and `-o`, and `(` / `)` (grouping) operators are XSI extensions to the POSIX standard. All are marked as obsolescent in POSIX-2008. They should not be used in new code. One of the practical problems with `[ A = B -a C = D ]` (or `-o`) is that [[http://www.opengroup.org/onlinepubs/9699919799/utilities/test.html|POSIX does not specify]] the results of a `test` or `[` command with more than 4 arguments. It probably works in most shells, but you can't count on it. If you have to write for POSIX shells, then you should use two `test` or `[` commands separated by a `&&` operator instead. <<Anchor(pf7)>> == [[ $foo > 7 ]] == There are multiple issues here. First, the [[BashFAQ/031|[[ command]] should ''not'' be used solely for evaluating [[ArithmeticExpression|arithmetic expressions]]. It should be used for test expressions involving one of the supported test operators. Though technically you ''can'' do math using some of `[[`'s operators, it only makes sense to do so in conjunction with one of the non-math test operators somewhere in the expression. If you just want to do a numeric comparison (or any other shell arithmetic), it is much better to just use `(( ))` instead: <pre> # Bash / Ksh ((foo > 7)) # Right! [[ foo -gt 7 ]] # Works, but is pointless. Most will consider it wrong. Use ((...)) or let instead. </pre> If you use the `>` operator inside `[[ ]]`, it's treated as a string comparison (test for collation order by locale), ''not'' an integer comparison. This may work sometimes, but it will fail when you least expect it. If you use `>` inside `[ ]`, it's even worse: it's an output redirection. You'll get a file named `7` in your directory, and the test will succeed as long as `$foo` is not empty. If strict POSIX-conformance is a requirement, and `((` is not available, then the correct alternative using old-style `[` is <pre> # POSIX [ "$foo" -gt 7 ] # Also right! [ $((foo > 7)) -ne 0 ] # POSIX-compatible equivalent to ((, for more general math operations. </pre> Note that the `test ... -gt` command will fail in interesting ways if `$foo` is [[BashFAQ/054|not an integer]]. Therefore, there's not much point in quoting it properly other than for performance and to confine the arguments to a single word to reduce the likelihood of obscure side-effects possible in some shells. If the input to any arithmetic context (including `((` or `let`), or `[` test expression involving numeric comparisons can't be guaranteed then you must ''always'' [[BashFAQ/054|validate your input before evaluating the expression]]. <pre> # POSIX case $foo in *[![:digit:]]*) printf '$foo expanded to a non-digit: %s\n' "$foo" >&2 exit 1 ;; *) [ $foo -gt 7 ] esac </pre> <<Anchor(pf8)>> == grep foo bar | while read -r; do ((count++)); done == The code above looks OK at first glance, doesn't it? Sure, it's just a poor implementation of `grep -c`, but it's intended as a simplistic example. Changes to `count` won't propagate outside the `while` loop because each command in a pipeline is executed in a separate SubShell. This surprises almost every Bash beginner at some point. POSIX doesn't specify whether or not the last element of a pipeline is evaluated in a subshell. Some shells such as ksh93 and Bash >= 4.2 with `shopt -s lastpipe` enabled will run the `while` loop in this example in the original shell process, allowing any side-effects within to take effect. Therefore, portable scripts must be written in such a way as to not depend upon either behavior. For workarounds for this and similar issues, please see [[BashFAQ/024|Bash FAQ #24]]. It's a bit too long to fit here. <<Anchor(pf9)>> == if [grep foo myfile] == Many beginners have an incorrect intuition about `if` statements brought about by seeing the very common pattern of an `if` keyword followed immediately by a `[` or `[[`. This convinces people that the `[` is somehow part of the `if` statement's syntax, just like parentheses used in C's `if` statement. This is ''not'' the case! `if` takes a ''command''. `[` is a command, not a syntax marker for the `if` statement. It's equivalent to the `test` command, except that the final argument must be a `]`. For example: <pre> # POSIX if [ false ]; then echo "HELP"; fi if test false; then echo "HELP"; fi </pre> are equivalent -- both checking that the argument "false" is non-empty. In both cases HELP will always be printed, to the surprise of programmers from other languages guessing about shell syntax. The syntax of an `if` statement is: <pre> if COMMANDS then <COMMANDS> elif <COMMANDS> # optional then <COMMANDS> else <COMMANDS> # optional fi # required </pre> Once again, `[` is a command. It takes arguments like any other regular ''simple command''. `if` is a ''compound command'' which contains other commands -- and '''there is no [''' in its syntax! While bash has a builtin command `[` and thus `knows` about `[` it has nothing special to do with `]`. Bash only passes `]` as argument to the `[` command, which requires `]` to be the last argument only to make scripts look better. There may be zero or more optional `elif` sections, and one optional `else` section. The `if` compound command is made up of two or more sections containing ''lists'' of commands, each delimited by a `then`, `elif`, or `else` keyword, and is terminated by the `fi` keyword. The exit status of the final command of the first section and each subsequent `elif` section determines whether each corresponding `then` section is evaluated. Another `elif` is evaluated until one of the `then` sections is executed. If no `then` section is evaluated, then the `else` branch is taken, or if no `else` is given, the `if` block is complete and the overall `if` command returns 0 (true). If you want to make a decision based on the output of a `grep` command, you do ''not'' want to enclose it in parentheses, brackets, backticks, or ''any other'' syntax! Just use `grep` as the `COMMANDS` after the `if`, like this: <pre> if grep -q fooregex myfile; then ... fi </pre> If the `grep` matches a line from `myfile`, then the exit code will be 0 (true), and the `then` part will be executed. Otherwise, if there are no matches, `grep` will return non-zero and the overall `if` command will be zero. '''See also:''' * BashGuide/TestsAndConditionals * http://wiki.bash-hackers.org/syntax/ccmd/if_clause <<Anchor(pf10)>> == if [bar="$foo"]; then ... == <pre> [bar="$foo"] # Wrong! [ bar="$foo" ] # Still wrong! </pre> As explained in the previous example, `[` is a command (which can be proven with `type -t [` or `whence -v [`). Just like with any other simple command, Bash expects the command to be followed by a space, then the first argument, then another space, etc. You can't just run things all together without putting the spaces in! Here is the correct way: <pre> if [ bar = "$foo" ]; then ... </pre> Each of `bar`, `=`, the expansion of `"$foo"`, and `]` is a separate [[Arguments|argument]] to the `[` command. There must be whitespace between each pair of arguments, so the shell knows where each argument begins and ends. <<Anchor(pf11)>> == if [ [ a = b ] && [ c = d ] ]; then ... == Here we go again. `[` is a ''command''. It is not a syntactic marker that sits between `if` and some sort of C-like "condition". Nor is it used for grouping. You cannot take C-like `if` commands and translate them into Bash commands just by replacing parentheses with square brackets! If you want to express a compound conditional, do this: <pre> if [ a = b ] && [ c = d ]; then ... </pre> Note that here we have two ''commands'' after the `if`, joined by an `&&` (logical AND, shortcut evaluation) operator. It's precisely the same as: <pre> if test a = b && test c = d; then ... </pre> If the first `test` command returns false, the body of the `if` statement is not entered. If it returns true, then the second `test` command is run; and if that also one returns true, then the body of the `if` statement ''will'' be entered. (C programmers are already familiar with `&&`. Bash uses the same ''short-circuit evaluation''. Likewise `||` does short-circuit evaluation for the ''OR'' operation.) The [[BashFAQ/031|[[ keyword]] ''does'' permit the use of `&&`, so it could also be written this way: <pre> if [[ a = b && c = d ]]; then ... </pre> See [[#pf6|pitfall #6]] for a pitfall related to ''tests'' combined with conditional operators. <<Anchor(pf12)>> == read $foo == You don't use a `$` before the variable name in a `read` command. If you want to put data into the variable named `foo`, you do it like this: . <pre> read foo </pre> Or more safely: . <pre> IFS= read -r foo </pre> `read $foo` would read a line of input and put it in the variable(s) whose name(s) are in `$foo`. This might be useful if you actually intended `foo` to be a [[BashFAQ/006|reference]] to some other variable; but in the majority of cases, this is simply a bug. <<Anchor(pf13)>> == cat file | sed s/foo/bar/ > file == You '''cannot''' read from a file and write to it in the same pipeline. Depending on what your pipeline does, the file may be clobbered (to 0 bytes, or possibly to a number of bytes equal to the size of your operating system's pipeline buffer), or it may grow until it fills the available disk space, or reaches your operating system's file size limitation, or your quota, etc. If you want to make a change to a file safely, other than appending to the end of it, use a text editor. . <pre> printf %s\\n ',s/foo/bar/g' w q | ed -s file </pre> If you are doing something that cannot be done with a text editor there ''must'' be a temporary file created at some point(*). For example, the following is completely portable: . <pre> sed 's/foo/bar/g' file > tmpfile && mv tmpfile file </pre> The following will ''only'' work on GNU sed 4.x: . <pre> sed -i 's/foo/bar/g' file(s) </pre> Note that this also creates a temporary file, and does the same sort of renaming trickery -- it just handles it transparently. And the following equivalent command requires perl 5.x (which is probably more widely available than GNU sed 4.x): . <pre> perl -pi -e 's/foo/bar/g' file(s) </pre> For more details on replacing contents of files, please see [[BashFAQ/021|Bash FAQ #21]]. (*) `sponge` from [[http://packages.debian.org/sid/moreutils|moreutils]] uses this example in its manual: . <pre> sed '...' file | grep '...' | sponge file </pre> Rather than using a temporary file plus an atomic `mv`, this version "soaks up" (the actual description in the manual!) all the data, before opening and writing to the `file`. This version will cause data loss if the program or system crashes during the write operation, because there's no copy of the original file on disk at that point. Using a temporary file + `mv` still incurs a slight risk of data loss in case of a system crash / power loss; to be 100% certain that either the old or the new file will survive a power loss, you must use `sync` before the `mv`. <<Anchor(pf14)>> == echo $foo == This relatively innocent-looking command causes ''massive'' confusion. Because the `$foo` isn't [[Quotes|quoted]], it will not only be subject to WordSplitting, but also file [[glob|globbing]]. This misleads Bash programmers into thinking their variables ''contain'' the wrong values, when in fact the variables are OK -- it's just the word splitting or filename expansion that's messing up their view of what's happening. . <pre> msg="Please enter a file name of the form *.zip" echo $msg </pre> This message is split into words and any globs are expanded, such as the *.zip. What will your users think when they see this message: . <pre> Please enter a file name of the form freenfss.zip lw35nfss.zip </pre> To demonstrate: . <pre> var="*.zip" # var contains an asterisk, a period, and the word "zip" echo "$var" # writes *.zip echo $var # writes the list of files which end with .zip </pre> In fact, the `echo` command cannot be used with absolute safety here. If the variable contains `-n` for example, `echo` will consider that an option, rather than data to be printed. The only absolutely ''sure'' way to print the value of a variable is using `printf`: . <pre> printf "%s\n" "$foo" </pre> <<Anchor(pf15)>> == $foo=bar == No, you don't assign a variable by putting a `$` in front of the variable name. This isn't perl. <<Anchor(pf16)>> == foo = bar == No, you can't put spaces around the `=` when assigning to a variable. This isn't C. When you write `foo = bar` the shell splits it into three words. The first word, `foo`, is taken as the command name. The second and third become the arguments to that command. Likewise, the following are also wrong: . <pre> foo= bar # WRONG! foo =bar # WRONG! $foo = bar; # COMPLETELY WRONG! foo=bar # Right. foo="bar" # More Right. </pre> <<Anchor(pf17)>> == echo <<EOF == A here document is a useful tool for embedding large blocks of textual data in a script. It causes a redirection of the lines of text in the script to the standard input of a command. Unfortunately, `echo` is not a command which reads from stdin. . <pre> # This is wrong: echo <<EOF Hello world How's it going? EOF # This is what you were trying to do: cat <<EOF Hello world How's it going? EOF # Or, use quotes which can span multiple lines (efficient, echo is built-in): echo "Hello world How's it going?" </pre> Using quotes like that is fine -- it works great, in all shells -- but it doesn't let you just drop a block of lines into the script. There's syntactic markup on the first and last line. If you want to have your lines untouched by shell syntax, and don't want to spawn a `cat` command, here's another alternative: . <pre> # Or use printf (also efficient, printf is built-in): printf %s "\ Hello world How's it going? " </pre> In the `printf` example, the `\` on the first line prevents an extra newline at the beginning of the text block. There's a literal newline at the end (because the final quote is on a new line). The lack of `\n` in the printf format argument prevents `printf` adding an extra newline at the end. The `\` trick won't work in single quotes. If you need/want single quotes around the block of text, you have two choices, both of which necessitate shell syntax "contaminating" your data: . <pre> printf %s \ 'Hello world ' printf %s 'Hello world ' </pre> <<Anchor(pf18)>> == su -c 'some command' == This syntax is ''almost'' correct. The problem is, on many platforms, `su` takes a `-c` argument, but it's not the one you want. For example, on OpenBSD: . <pre> $ su -c 'echo hello' su: only the superuser may specify a login class </pre> You want to pass `-c 'some command'` to a shell, which means you need a username before the `-c`. . <pre> su root -c 'some command' # Now it's right. </pre> `su` assumes a username of root when you omit one, but this falls on its face when you want to pass a command to the shell afterward. You must supply the username in this case. <<Anchor(pf19)>> == cd /foo; bar == If you don't check for errors from the `cd` command, you might end up executing `bar` in the wrong place. This could be a major disaster, if for example `bar` happens to be `rm -f *`. You must '''always''' check for errors from a `cd` command. The simplest way to do that is: . <pre> cd /foo && bar </pre> If there's more than just one command after the `cd`, you might prefer this: . <pre> cd /foo || exit 1 bar baz bat ... # Lots of commands. </pre> `cd` will report the failure to change directories, with a stderr message such as "bash: cd: /foo: No such file or directory". If you want to add your own message in stdout, however, you could use command grouping: . <pre> cd /net || { echo >&2 "Can't read /net. Make sure you've logged in to the Samba network, and try again."; exit 1; } do_stuff more_stuff </pre> Note there's a required space between `{` and `echo`, and a required `;` before the closing `}`. You could also write a `die` function, if you prefer. Some people also like to enable [[BashFAQ/105|set -e]] to make their scripts abort on ''any'' command that returns non-zero, but this can be [[BashFAQ/105|rather tricky to use correctly]] (since many common commands may return a non-zero for a warning condition, which you may not want to treat as fatal). By the way, if you're changing directories a lot in a Bash script, be sure to read the Bash help on `pushd`, `popd`, and `dirs`. Perhaps all that code you wrote to manage `cd`'s and `pwd`'s is completely unnecessary. Speaking of which, compare this: . <pre> find ... -type d -print0 | while IFS= read -r -d '' subdir; do here=$PWD cd "$subdir" && whatever && ... cd "$here" done </pre> With this: . <pre> find ... -type d -print0 | while IFS= read -r -d '' subdir; do (cd "$subdir" || exit; whatever; ...) done </pre> Forcing a SubShell here causes the `cd` to occur only in the subshell; for the next iteration of the loop, we're back to our normal location, regardless of whether the `cd` succeeded or failed. We don't have to change back manually, and we aren't stuck in a neverending string of `... && ...` logic preventing the use of other conditionals. The subshell version is simpler and cleaner (albeit a tiny bit slower). Another approach is to `cd` unconditionally to where we're supposed to be, at the start of each loop iteration: . <pre> here=$PWD find ... -type d -print0 | while IFS= read -r -d '' subdir; do cd "$here" || continue cd "$subdir" || continue whatever ... done </pre> At least this way, we can `continue` to the next loop iteration and don't have to string an indefinite series of `&&` together to ensure that we reach the `cd` at the end of the loop body. <<Anchor(pf20)>> == [ bar == "$foo" ] == The `==` operator is not valid for the POSIX `[` command. Use `=` or the [[BashFAQ/031|[[ keyword]] instead. . <pre> [ bar = "$foo" ] && echo yes [[ bar == $foo ]] && echo yes </pre> In Bash, `[ "$x" == y ]` is accepted as an extension, which often leads Bash programmers to think it's the correct syntax. It's not; it's a [[Bashism]]. If you're going to use Bashisms, you might as well just use `[[` instead. <<Anchor(pf21)>> == for i in {1..10}; do ./something &; done == You ''cannot'' put a `;` immediately after an `&`. Just remove the extraneous `;` entirely. . <pre> for i in {1..10}; do ./something & done </pre> Or: . <pre> for i in {1..10}; do ./something & done </pre> `&` already functions as a command terminator, just like `;` does. And you cannot mix the two. In general, a `;` can be replaced by a newline, but not all newlines can be replaced by `;`. <<Anchor(pf22)>> == cmd1 && cmd2 || cmd3 == Some people try to use `&&` and `||` as a shortcut syntax for `if ... then ... else ... fi`, perhaps because they think they are being clever. For instance, . <pre> # WRONG! [[ -s $errorlog ]] && echo "Uh oh, there were some errors." || echo "Successful." </pre> However, this construct is ''not'' completely equivalent to `if ... fi` in the general case. The command that comes after the `&&` also generates an exit status, and if that exit status isn't "true" (0), then the command that comes after the `||` will ''also'' be invoked. For example: . <pre> i=0 true && ((i++)) || ((i--)) # WRONG! echo "$i" # Prints 0 </pre> What happened here? It looks like `i` should be 1, but it ends up 0. Why? Because both the `i++` ''and'' the `i--` were executed. The `((i++))` command has an exit status, and that exit status is derived from a C-like evaluation of the expression inside the parentheses. That expression's value happens to be 0 (the initial value of `i`), and in C, an expression with an integer value of 0 is considered ''false''. So `((i++))` (when `i` is 0) has an exit status of 1 (false), and therefore the `((i--))` command is executed as well. Another clever person thinks that we can fix it by using the pre-increment operator, since the exit status from `++i` (with `i` initially 0) is true: . <pre> i=0 true && (( ++i )) || (( --i )) # STILL WRONG! echo "$i" # Prints 1 by dumb luck </pre> But that's missing the point of the example. It just ''happens'' to work by ''coincidence'', and you ''cannot'' rely on `x && y || z` if `y` has '''any''' chance of failure! (This example still fails if we initialize `i` to -1 instead of 0.) If you need safety, or if you simply aren't sure how this works, or if ''anything'' in the preceding paragraphs wasn't completely clear, please just use the simple `if ... fi` syntax in your programs. . <pre> i=0 if true; then ((i++)) else ((i--)) fi echo "$i" # Prints 1 </pre> This section also applies to Bourne shell, here is the code that illustrates it: . <pre> # WRONG! true && { echo true; false; } || { echo false; true; } </pre> Output is two lines "true" and "false", instead the single line "true". <<Anchor(pf23)>> == echo "Hello World!" == The problem here is that, in an interactive Bash shell (in versions prior to 4.3), you'll see an error like: . <pre> bash: !": event not found </pre> This is because, in the default settings for an interactive shell, Bash performs csh-style history expansion using the exclamation point. This is '''not''' a problem in shell scripts; only in interactive shells. Unfortunately, the obvious attempt to "fix" this won't work: . <pre> $ echo "hi\!" hi\! </pre> The easiest solution is unsetting the `histexpand` option: this can be done with `set +H` or `set +o histexpand` . Question: Why is playing with `histexpand` more apropriate than single quotes? . ''I personally ran into this issue when I was manipulating song files, using commands like'' <pre> mp3info -t "Don't Let It Show" ... mp3info -t "Ah! Leah!" ... </pre> ''Using single quotes is extremely inconvenient because of all the songs with apostrophes in their titles. Using double quotes ran into the history expansion issue. (And imagine a file that has both in its name. The quoting would be atrocious.) Since I never actually ''use'' history expansion, my personal preference was to turn it off in `~/.bashrc`.'' -- GreyCat These solutions will work: . <pre> echo 'Hello World!' </pre> or . <pre> set +H echo "Hello World!" </pre> or . <pre> histchars= </pre> Many people simply choose to put `set +H` or `set +o histexpand` in their `~/.bashrc` to deactivate history expansion permanently. This is a personal preference, though, and you should choose whatever works best for you. Another solution is: . <pre> exmark='!' echo "Hello, world$exmark" </pre> In Bash 4.3 and newer, a double quote following `!` no longer triggers history expansion, but history expansion is still performed within double quotes, so while `echo "Hello World!"` is OK, these will still be a problem: . <pre> echo "Hello, World!(and the rest of the Universe)" echo "foo!'bar'" </pre> <<Anchor(pf24)>> == for arg in $* == Bash (like all Bourne shells) has a special syntax for referring to the list of positional parameters one at a time, and `$*` isn't it. Neither is `$@`. Both of those expand to the list of words in your script's parameters, not to each parameter as a separate word. The correct syntax is: . <pre> for arg in "$@" # Or simply: for arg </pre> Since looping over the positional parameters is such a common thing to do in scripts, `for arg` defaults to `for arg in "$@"`. The double-quoted `"$@"` is special magic that causes each parameter to be used as a single word (or a single loop iteration). It's what you should be using at least 99% of the time. Here's an example: . <pre> # Incorrect version for x in $*; do echo "parameter: '$x'" done $ ./myscript 'arg 1' arg2 arg3 parameter: 'arg' parameter: '1' parameter: 'arg2' parameter: 'arg3' </pre> It should have been written: . <pre> # Correct version for x in "$@"; do echo "parameter: '$x'" done # or better: for x do echo "parameter: '$x'" done $ ./myscript 'arg 1' arg2 arg3 parameter: 'arg 1' parameter: 'arg2' parameter: 'arg3' </pre> <<Anchor(pf25)>> == function foo() == This works in some shells, but not in others. You should ''never'' combine the keyword `function` with the parentheses `()` when defining a function. Bash (at least some versions) will allow you to mix the two. Most of the shells won't accept that (zsh 4.x and perhaps above will - for example). Some shells will accept `function foo`, but for maximum portability, you should always use: . <pre> foo() { ... } </pre> <<Anchor(pf26)>> == echo "~" == Tilde expansion only applies when '~' is unquoted. In this example echo writes '~' to stdout, rather than the path of the user's home directory. Quoting path parameters that are expressed relative to a user's home directory should be done using $HOME rather than '~'. For instance consider the situation where $HOME is "/home/my photos". . <pre> "~/dir with spaces" # expands to "~/dir with spaces" ~"/dir with spaces" # expands to "~/dir with spaces" ~/"dir with spaces" # expands to "/home/my photos/dir with spaces" "$HOME/dir with spaces" # expands to "/home/my photos/dir with spaces" </pre> <<Anchor(pf27)>> == local varname=$(command) == When declaring a local variable in a function, the `local` acts as a command in its own right. This can sometimes interact oddly with the rest of the line -- for example, if you wanted to capture the exit status (`$?`) of the CommandSubstitution, you can't do it. `local`'s exit status masks it. It's best to use separate commands for this: . <pre> local varname varname=$(command) rc=$? </pre> This is also true of `export`, which will similarly mask the exit status. The next pitfall describes another issue with this syntax: <<Anchor(pf28)>> == export foo=~/bar == [[TildeExpansion|Tilde expansion]] (with or without a username) is only guaranteed to occur when the tilde appears at the beginning of a [[Arguments|word]], either by itself or followed by a slash. It is also guaranteed to occur when the tilde appears immediately after the `=` in an assignment. However, the `export` and `local` commands ''do not constitute an assignment''. So, in some shells (like Bash), `export foo=~/bar` will undergo tilde expansion; in others (like dash), it will not. . <pre> foo=~/bar; export foo # Right! export foo="$HOME/bar" # Right! </pre> <<Anchor(pf29)>> == sed 's/$foo/good bye/' == In [[Quotes|single quotes]], bash parameter expansions like `$foo` do not get expanded. That is the purpose of single quotes, to protect characters like `$` from the shell. Change the quotes to double quotes: . <pre> foo="hello"; sed "s/$foo/good bye/" </pre> But keep in mind, if you use double quotes you might need to use more escapes. See the [[Quotes]] page. <<Anchor(pf30)>> == tr [A-Z] [a-z] == There are (at least) three things wrong here. The first problem is that `[A-Z]` and `[a-z]` are seen as [[glob]]s by the shell. If you don't have any single-lettered filenames in your current directory, it'll seem like the command is correct; but if you do, things will go wrong. Probably at 0300 hours on a weekend. The second problem is that this is not really the correct notation for `tr`. What this actually does is translate '[' into '['; anything in the range A-Z into a-z; and ']' into ']'. So you don't even need those brackets, and the first problem goes away. The third problem is that depending on the [[locale]], A-Z or a-z may not give you the 26 ASCII characters you were expecting. In fact, in some locales z is in the middle of the alphabet! The solution to this depends on what you want to happen: . <pre> # Use this if you want to change the case of the 26 latin letters LC_COLLATE=C tr A-Z a-z # Use this if you want the case conversion to depend upon the locale, which might be more like what a user is expecting tr '[:upper:]' '[:lower:]' </pre> The quotes are required on the second command, to avoid [[glob|globbing]]. <<Anchor(pf31)>> == ps ax | grep gedit == The fundamental problem here is that the name of a running process is inherently unreliable. There could be more than one legitimate gedit process. There could be something else disguising itself as gedit (changing the reported name of an executed command is trivial). For ''real'' answers to this, see ProcessManagement. The following is the quick and dirty stuff. Searching for the PID of (for example) gedit, many people start with <pre> $ ps ax | grep gedit 10530 ? S 6:23 gedit 32118 pts/0 R+ 0:00 grep gedit </pre> which, depending on a RaceCondition, often yields grep itself as a result. To filter grep out: <pre> ps ax | grep -v grep | grep gedit # will work, but ugly </pre> An alternative to this is to use: <pre> ps ax | grep '[g]edit' # quote to avoid shell GLOB </pre> This will ignore the grep itself in the process table as that is [g]edit and grep is looking for gedit once evaluated. On GNU/Linux, the parameter -C can be used instead to filter by commandname: <pre> $ ps -C gedit PID TTY TIME CMD 10530 ? 00:06:23 gedit </pre> But why bother when you could just use pgrep instead? <pre> $ pgrep gedit 10530 </pre> Now in a second step the PID is often extracted by awk or cut: <pre> $ ps -C gedit | awk '{print $1}' | tail -n1 </pre> but even that can be handled by some of the trillions of parameters for ps: <pre> $ ps -C gedit -opid= 10530 </pre> If you're stuck in 1992 and aren't using pgrep, you could use the ancient, obsolete, deprecated pidof (GNU/Linux only) instead: <pre> $ pidof gedit 10530 </pre> and if you need the PID to kill the process, ''pkill'' might be interesting for you. Note however that, for example, `pgrep/pkill ssh` would also find processes named sshd, and you wouldn't want to kill those. Unfortunately some programs aren't started with their name, for example firefox is often started as firefox-bin, which you would need to find out with - well - '''ps ax | grep firefox'''. :) Or, you can stick with pgrep by adding some parameters: <pre> $ pgrep -fl firefox 3128 /usr/lib/firefox/firefox 7120 /usr/lib/firefox/plugin-container /usr/lib/flashplugin-installer/libflashplayer.so -greomni /usr/lib/firefox/omni.ja 3128 true plugin </pre> Please read ProcessManagement. Seriously. <<Anchor(pf32)>> == printf "$foo" == This isn't wrong because of [[Quotes|quotes]], but because of a ''format string exploit''. If `$foo` is not strictly under your control, then any `\` or `%` characters in the variable may cause undesired behavior. Always supply your own format string: <pre> printf %s "$foo" printf '%s\n' "$foo" </pre> <<Anchor(pf33)>> == for i in {1..$n} == The BashParser performs BraceExpansion ''before'' any other expansions or substitutions. So the brace expansion code sees the literal `$n`, which is not numeric, and therefore it doesn't expand the curly braces into a list of numbers. This makes it nearly impossible to use brace expansion to create lists whose size is only known at run-time. Do this instead: <pre> for ((i=1; i<=n; i++)); do ... done </pre> In the case of simple iteration over integers, an arithmetic `for` loop should almost always be preferred over brace expansion to begin with, because brace expansion pre-expands every argument which can be slower and unnecessarily consumes memory. <<Anchor(pf34)>> == if [[ $foo = $bar ]] (depending on intent) == When the right-hand side of an `=` operator inside [[BashFAQ/031|[[]] is not quoted, bash does [[glob|pattern matching]] against it, instead of treating it as a string. So, in the code above, if `bar` contains `*`, the result will ''always'' be true. If you want to check for equality of strings, the right-hand side should be quoted: <pre> if [[ $foo = "$bar" ]] </pre> If you want to do pattern matching, it might be wise to choose variable names that indicate the right-hand side contains a pattern. Or use comments. It's also worth pointing out that if you quote the right-hand side of `=~` it ''also'' forces a simple string comparison, rather than a regular expression matching. This leads us to: <<Anchor(pf35)>> == if [[ $foo =~ 'some RE' ]] == The quotes around the right-hand side of the `=~` operator cause it to become a string, rather than a RegularExpression. If you want to use a long or complicated regular expression and avoid lots of backslash escaping, put it in a variable: <pre> re='some RE' if [[ $foo =~ $re ]] </pre> This also works around the difference in how `=~` works across different versions of bash. Using a variable avoids some nasty and subtle problems. The same problem occurs with [[glob|pattern matching]] inside `[[`: <pre> [[ $foo = "*.glob" ]] # Wrong! *.glob is treated as a literal string. [[ $foo = *.glob ]] # Correct. *.glob is treated as a glob-style pattern. </pre> <<Anchor(pf36)>> == [ -n $foo ] or [ -z $foo ] == When using the `[` command, you '''must''' [[Quotes|quote]] each substitution that you give it. Otherwise, `$foo` could expand to 0 words, or 42 words, or any number of words that isn't 1, which breaks the syntax. <pre> [ -n "$foo" ] [ -z "$foo" ] [ -n "$(some command with a "$file" in it)" ] # [[ doesn't perform word-splitting or glob expansion, so you could also use: [[ -n $foo ]] [[ -z $foo ]] </pre> <<Anchor(pf37)>> == [[ -e "$broken_symlink" ]] returns 1 even though $broken_symlink exists == Test follows symlinks, therefore if a symlink is broken, i.e. it points to a file that doesn't exists or is in a directory you don't have access to, test -e returns 1 for it even though it exists. In order to work around it (and prepare against it) you should use: <pre> # bash/ksh/zsh [[ -e "$broken_symlink" || -L "$broken_symlink" ]] # POSIX sh+test [ -e "$broken_symlink" ] || [ -L "$broken_symlink" ] </pre> <<Anchor(pf38)>> == ed file <<<"g/d\{0,3\}/s//e/g" fails == The problem caused because ed doesn't accept 0 for \{0,3\}. You can check that the following do work: <pre> ed file <<<"g/d\{1,3\}/s//e/g" </pre> Note that this happens even though POSIX states that BRE (which is the Regular Expression flavor used by ed) [[http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_06|should accept 0 as the minimum number of occurrences (see section 5)]]. <<Anchor(pf39)>> == expr sub-string fails for "match" == This works reasonably well ---- most of the time <pre> word=abcde expr "$word" : ".\(.*\)" bcde </pre> But WILL fail for the word "match" <pre> word=match expr "$word" : ".\(.*\)" </pre> The problem is "match" is a keyword. Solution (GNU only) is prefix with a '+' <pre> word=match expr + "$word" : ".\(.*\)" atch </pre> Or, y'know, stop using `expr`. You can do everything `expr` does by using [[BashFAQ/073|Parameter Expansion]]. What's that thing up there trying to do? Remove the first letter of a word? That can be done in POSIX shells using PE or Substring Expansion: <pre> $ word=match $ echo "${word#?}" # PE atch $ echo "${word:1}" # SE atch </pre> Seriously, there's no excuse for using `expr` unless you're on Solaris with its non-POSIX-conforming `/bin/sh`. It's an external process, so it's much slower than in-process string manipulation. And since nobody uses it, nobody understands what it's doing, so your code is obfuscated and hard to maintain. <<Anchor(pf40)>> == On UTF-8 and Byte-Order Marks (BOM) == '''In general:''' Unix UTF-8 text does not use BOM. The encoding of plain text is determined by the locale or by mime types or other metadata. While the presence of a BOM would not normally damage a UTF-8 document meant only for reading by humans, it is problematic (often syntactically illegal) in any text file meant to be interpreted by automated processes such as scripts, source code, configuration files, and so on. Files starting with BOM should be considered equally foreign as those with MS-DOS linebreaks. '''In shell scripting:''' 'Where UTF-8 is used transparently in 8-bit environments, the use of a BOM will interfere with any protocol or file format that expects specific ASCII characters at the beginning, such as the use of "#!" of at the beginning of Unix shell scripts.' http://unicode.org/faq/utf_bom.html#bom5 <<Anchor(pf41)>> == content=$(<file) == There isn't anything wrong with this expression, but you should be aware that command substitutions (all forms: <pre>`...`</pre>, `$(...)`, `$(<file)`, <pre>`<file`</pre>, and `${ ...; }` (ksh)) remove any trailing newlines. This is often inconsequential or even desirable, but if you must preserve the literal output including any possible trailing newlines, it gets tricky because you have no way of knowing whether the output had them or how many. One ugly but usable workaround is to add a postfix inside the command substitution and remove it on the outside: <pre> absolute_dir_path_x=$(readlink -fn -- "$dir_path"; printf x) absolute_dir_path=${absolute_dir_path_x%x} </pre> A less portable but arguably prettier solution is to use `read` with an empty delimiter. <pre> # Ksh (or bash 4.2+ with lastpipe enabled) readlink -fn -- "$dir_path" | IFS= read -rd '' absolute_dir_path </pre> The downside to this method is that the `read` will always return false unless the command outputs a NUL byte causing only part of the stream to be read. The only way to get the exit status of the command is through `PIPESTATUS`. You could also intentionally output a NUL byte to force `read` to return true, and use `pipefail`. <pre> set -o pipefail { readlink -fn -- "$dir_path"; printf '\0x'; } | IFS= read -rd '' absolute_dir_path </pre> This is somewhat of a portability mess, as Bash supports both `pipefail` and `PIPESTATUS`, ksh93 supports `pipefail` only, and only recent versions of mksh support `pipefail`, while earlier versions supported `PIPESTATUS` only. Additionally, a bleeding-edge ksh93 version is required in order for `read` to stop at the NUL byte. <<Anchor(pf42)>> == for file in ./* ; do if [[ $file != *.* ]] == One way to prevent programs from interpreting filenames passed to them as options is to use pathnames (see [[#pf3|pitfall #3]] above). For files under the current directory, names may be prefixed with a relative pathname `./`. In the case of a pattern like `*.*` however, problems can arise because it matches a string of the form `./filename`. In a simple case, you can just use the glob directly to generate the desired matches. If however a separate pattern-matching step is required (e.g. the results have been preprocessed and stored in an array, and need to be filtered), it could be solved by taking the prefix into account in the pattern: `[[ $file != ./*.* ]]`, or by stripping the pattern from the match. <pre> # Bash shopt -s nullglob for path in ./*; do [[ ${path##*/} != *.* ]] && rm "$path" done # Or even better for file in *; do [[ $file != *.* ]] && rm "./$file" done # Or better still for file in *.*; do rm "./$file" done </pre> Another possibility is to signal the ''end of options'' with a `--` argument. (Again, covered in [[#pf3]]). <pre> shopt -s nullglob for file in *; do [[ $file != *.* ]] && rm -- "$file" done </pre> <<Anchor(pf43)>> == somecmd 2>&1 >>logfile == This is by far the most common mistake involving redirections, typically performed by someone wanting to direct both stdout and stderr to a file or pipe will try this and not understand why stderr is still showing up on their terminal. If you're perplexed by this, you probably don't understand how [[http://wiki.bash-hackers.org/howto/redirection_tutorial|redirections]] or possibly [[FileDescriptor|file descriptors]] work to begin with. Redirections are evaluated left-to-right before the command is executed. This semantically incorrect code essentially means: "first redirect standard error to where standard out is currently pointing (the tty), then redirect standard out to logfile". This is backwards. Standard error is already going to the tty. Use the following instead: <pre> somecmd >>logfile 2>&1 </pre> See [[BashFAQ/055|a more in-depth explanation]], [[http://wiki.bash-hackers.org/scripting/copydescriptor|Copy descriptor explained]], and [[BashGuide/InputAndOutput#Redirection|BashGuide - redirection]]. <<Anchor(pf44)>> == cmd; (( ! $? )) || die == `$?` is only required if you need to retrieve the exact status of the previous command. If you only need to test for success or failure (any non-zero status), just test the command directly. e.g.: <pre> if cmd; then ... fi </pre> Checking an exit status against a list of alternatives might follow a pattern like this: <pre> cmd status=$? case $status in 0) echo success >&2 ;; 1) echo 'Must supply a parameter, exiting.' >&2 exit 1 ;; *) echo "Unknown error $status, exiting." >&2 exit "$status" esac </pre> <<Anchor(pf45)>> == y=$(( array[$x] )) == Due to [[http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_04|the POSIX wording]] of arithmetic expansion (which calls for expansion of command substitutions ''after'' parameter expansion), expansion of an array subscript inside an arithmetic expansion can lead to code injection exploits. Yeah, that's a lot of big, confusing words. Here's how it breaks: <pre> $ x='$(date >&2)' # redirection is just so we can see everything happen $ y=$((array[$x])) # array doesn't even have to exist Mon Jun 2 10:49:08 EDT 2014 </pre> Quoting `"$x"` won't help, either: <pre> $ y=$((array["$x"])) Mon Jun 2 10:51:03 EDT 2014 </pre> The two tricks that ''do'' work are: <pre> # 1. Escape the $x so it isn't expanded prematurely. $ y=$((array[\$x])) # 2. Use the full ${array[$x]} syntax. $ y=$((${array[$x]})) </pre> <<Anchor(pf46)>> == read num; echo $((num+1)) == Always validate your input (see [[BashFAQ/054]]) before using num in an arithmetic context as it allows code injection. <pre> $ echo 'a[$(echo injection >&2)]' | bash -c 'read num; echo $((num+1))' injection 1 </pre> <<Anchor(pf47)>> == IFS=, read -ra fields <<< "$csv_line" == Unbelievable as it may seem, POSIX requires the treatment of [[IFS]] as a field ''terminator'', rather than a field ''separator''. What this means in our example is that if there's an empty field at the end of the input line, it will be discarded: <pre> $ IFS=, read -ra fields <<< "a,b," $ declare -p fields declare -a fields='([0]="a" [1]="b")' </pre> Where did the empty field go? It was eaten for historical reasons ("because it's always been that way"). This behavior is not unique to bash; all conformant shells do it. A non-empty field is properly scanned: <pre> $ IFS=, read -ra fields <<< "a,b,c" $ declare -p fields declare -a fields='([0]="a" [1]="b" [2]="c")' </pre> So, how do we work around this nonsense? As it turns out, appending an IFS character to the end of the input string will force the scanning to work. If there was a trailing empty field, the extra IFS character "terminates" it so that it gets scanned. If there was a trailing non-empty field, the IFS character creates a new, empty field that gets dropped. <pre> $ input="a,b," $ IFS=, read -ra fields <<< "$input," $ declare -p fields declare -a fields='([0]="a" [1]="b" [2]="")' </pre> <<Anchor(pf48)>> == export CDPATH=.:~/myProject == Do not export CDPATH. Setting CDPATH in .bashrc is not an issue, but exporting it will cause any bash or sh script you run, that happen to use `cd`, to potentially change behaviour. There are two problems. A script that does the following: <pre> cd some/dir || exit cmd to be run in some/dir </pre> may change directory to `~/myProject/some/dir` instead of `./some/dir`, depending on what directories exist at the time. So the `cd` may succeed and take the script to the wrong directory, with potentially harmful effects of the following commands which now run in a different directory than intended. The second problem is when `cd` is run in a context where the output is captured: <pre> output=$(cd some/dir && some command) </pre> As a side-effect when CDPATH is set, `cd` will output something like `/home/user/some/dir` to stdout to indicate that it found a directory through CDPATH, which in turn will end up in the output variable along with the intended output of `some command`. A script can make itself immune to a CDPATH inherited from the environment by always prepending `./` to relative paths, or run `unset CDPATH` at the start of the script, but don't assume every scripter has taken this pitfall into account, so don't export CDPATH. <<Anchor(pf49)>> == OIFS="$IFS"; ...; IFS="$OIFS" == Directly assigning a variable's value to a temporary variable isn't alone enough to restore its state. The assignment will always result in a ''set'' but ''empty'' temporary variable even if the initial variable was unset. This is a particular problem for IFS because an ''empty'' IFS has a completely different meaning from an ''unset'' IFS, and setting IFS to a temporary value for a command or two is a common requirement. An easy workaround is to designate a prefix to distinguish set from unset vars, then strip it when finished. <pre> # oIFS is unset or null implies IFS is null. typeset oIFS=${IFS+_${IFS}} IFS=/; echo "${array[*]}" ${oIFS:+'false'} unset -v IFS || IFS=${oIFS#_} </pre> A local variable is usually preferable when possible. <pre> f() { local IFS IFS=/; echo "${array[*]}" } f </pre> Subshells are another possibility. <pre> ( IFS=/; echo "${array[*]}" ) </pre> <<Anchor(pf50)>> == hosts=( $(aws ...) ) == It is not safe to populate an array with a raw `$(...)` CommandSubstitution. The output of the command undergoes word splitting (on ''all'' whitespace, even ones that are inside quotes) and then [[glob|globbing]]. If there's a word like `*` or `eh?` or `[abc]` in the result, it will be expanded based on filenames in the current working directory. To select a replacement, you need to know whether the command writes its output on a single line, or multiple lines. If it's a single line: <pre> read -ra hosts < <(aws ...) </pre> If it's multiple lines (and you're targeting bash 4.0 or later): <pre> readarray -t hosts < <(aws ...) </pre> If it's multiple lines (and you want compatibility with bash 3.x, ''or'' want your command's exit status to be reflected in success or failure of the `read` operation without depending on behavior only available in bash 4.4 and newer): <pre> IFS=$'\n' read -r -d '' -a hosts < <(aws ... && printf '\0') </pre> This will prevent globbing. It still won't help you if you needed to avoid splitting on quoted whitespace, but unfortunately ''nothing'' bash can do handles that case. For generalized CSV (comma-separated value) file handling, you really need to switch to a language that has a dedicated CSV input library. <<Anchor(pf51)>> == Non-atomic writes with xargs -P == GNU `xargs` supports running multiple jobs in parallel. `-P n` where '''n''' is the number of jobs to run in parallel. <pre> seq 100 | xargs -n1 -P10 echo "$a" | grep 5 seq 100 | xargs -n1 -P10 echo "$a" > myoutput.txt </pre> This will work fine for many situations but has a deceptive flaw: If `$a` contains more than ~1000 characters, the `echo` may not be atomic (it may be split into multiple `write()` calls), and there is a risk that two lines will be mixed. <pre> $ perl -e 'print "a"x2000, "\n"' > foo $ strace -e write bash -c 'read -r foo < foo; echo "$foo"' >/dev/null write(1, "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"..., 1008) = 1008 write(1, "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"..., 993) = 993 +++ exited with 0 +++ </pre> Obviously the same issue arises if there are multiple calls to `echo` or `printf`: <pre> slowprint() { printf 'Start-%s ' "$1" sleep "$1" printf '%s-End\n' "$1" } export -f slowprint seq 10 | xargs -n1 -I {} -P4 bash -c "slowprint {}" # Compare to no parallelization seq 10 | xargs -n1 -I {} bash -c "slowprint {}" # Be sure to see the warnings in the next Pitfall! </pre> Outputs from the parallel jobs are mixed together, because each job consists of two (or more) separate `write()` calls. If you need the outputs unmixed, it is therefore recommended to use a tool that guarantees output will be serialized (such as GNU Parallel). For further details see [[https://gist.github.com/ole-tange/88ae153797748b3618e2433377e2870a|a demonstration of the mixing problem]]. <<Anchor(pf52)>> == find . -exec sh -c 'echo {}' \; == This command contains a CodeInjection vulnerability. The filename that is found by `find` is injected into a shell command and parsed by `sh`. If the filename contains shell metacharacters like `;` or `$( ... )` then the filename may be ''executed as code'' by `sh'. The "slowprint" example in the previous Pitfall would have been a CodeInjection bug if the input weren't guaranteed to be integers. To be more precise, [[http://pubs.opengroup.org/onlinepubs/9699919799/utilities/find.html#tag_20_47|POSIX find]] does not specify whether an argument which contains ''more than'' just `{}` is expanded. GNU `find` allows this CodeInjection to occur. Other implementations choose a safer path: <pre> # uname -a HP-UX imadev B.10.20 A 9000/785 2008897791 two-user license # find /dev/null -exec sh -c 'echo {}' \; {} </pre> The correct approach is to ''separate'' the filename argument from the script argument: <pre> find . -exec sh -c 'echo "$1"' x {} \; </pre> <<Anchor(pf53)>> == sudo mycmd > /myfile == [[Redirection]] is done ''before'' the command is executed. Usually that doesn't matter, but with `sudo` we have a command being executed as a different user than the redirection. If the redirection must be executed with `sudo`-granted privileges, then you need a wrapper: <pre> sudo sh -c 'mycmd > /myfile' </pre> <<Anchor(pf54)>> == sudo ls /foo/* == This is very similar to the previous pitfall. [[glob|Globbing]] is also done ''before'' the command is executed. If the directory isn't readable by your normal user privileges, then you may need the globbing to be done in a shell that has the `sudo`-granted privileges: <pre> sudo sh -c 'ls /foo/*' </pre> <<Anchor(pf55)>> == myprogram 2>&- == '''Do not''' close stdin, stdout or stderr as a "shorthand" for redirecting to `/dev/null`. Write it out correctly. <pre> myprogram 2>/dev/null </pre> Why? Consider what happens when your program tries to write an error message to stderr. If stderr has been redirected to `/dev/null`, the write succeeds, and your program is free to carry on, secure in the knowledge that it has diligently reported the error condition. But if stderr has been ''closed'', then the write will fail. At that point, your program may do something unpredictable. It may carry on and ignore the failure, or it may immediately exit, considering the execution environment so broken that it cannot safely continue. Or whatever else the programmer decided the program should do when its world has become a dystopian hell. All programs are assured that stdin, stdout and stderr will ''exist'' and will be readable/writable in an appropriate and reasonable manner. By closing one of them, you have violated your promise to this program. This is not acceptable. Of course, an even better solution would be to actually log the errors somewhere, so you can go back and read them and figure out what's wrong. <<Anchor(pf56)>> == Using xargs without -0 == `xargs` splits on whitespace. This is unfortunate because whitespace is allowed in filenames and commonly used by GUI users. `xargs` also treats `'` and `"` specially, which can also lead to problems: <pre> touch Dad\'s\ \"famous\"\ 1\'\ pizza.txt touch Dad\'s\ 12\"\ records.txt touch 2\"x1\'\ wood.txt touch 2\"x4\"\ wood.txt </pre> Here `xargs` warns: <pre> # Do not do this $ find . -type f | xargs wc xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option </pre> Here `xargs` does not warn at all: <pre> # Do not do this echo * | xargs wc find *famous* -type f | xargs wc find *4* -type f | xargs wc </pre> Instead use `xargs -0`: <pre> # Do this instead printf '%s\0' * | xargs -0 wc find . -type f -name '*famous*' -print0 | xargs -0 wc find . -type f -name '*4*' -exec wc {} + </pre> If using `-0` is not simple, an alternative is to use GNU Parallel, which splits on \n. And while \n is also allowed in filenames they never occur unless your users are malicious. In any case: '''If''' you use `xargs` without `-0` put a comment in your code explaining why that is safe in your particular situation. ---- CategoryShell CategoryBashguide c8662dc32232b5ff7de10c449575d75a36bf9868 0 506 2821 2796 2025-02-18T12:31:05Z Pvdm 2 wikitext text/x-wiki {| class="wikitable sortable" |+ USB Drives Overzicht |- ! USB Stick !! Capacity !! speed !! Contents !! Remarks |- | Voyager || 8GB || 24 || Windows 10 home?? || Example |- | RedHat || 16 || 7 || Leap 15.5 || X86_64 |- | WitteSticker || 2 || 10-15 || GPartEd live 2024 || 20220202 |- | SanDisk || 32GB || 130 || KDE Live! TW || bootable |- | Ictivity || 3.8GB || ? || audioanalyzer files || FAT16 |- | Dupaco || 4GB || 3 || HANTEK || |- | openSUSE || 4GB || 26 || leeg || Example |- | Example || Example || Example || Example || Example |- | Example || Example || Example || Example || Example |- | Example || Example || Example || Example || Example |} = = <pre> drive (capacity): speed current image voyager(8): 24 win10 home? redhat(16): 7 opensuse tumbleweed 20180723 opensuse(4): 26 GPARTED Live 20200820 opensusekoord: supergrubbootdisk dupaco(4): 3 opensuse Leap 15.0 NET Sandisk(32): 130 kde live TW Emtec: Ansible cursus dump wittesticker(2): 10-15 measured on Envy. pi3:/etc/sysconfig/network # hdparm -t /dev/mmcblk0 /dev/mmcblk0: Timing buffered disk reads: 66 MB in 3.09 seconds = 21.39 MB/sec pi3:/etc/sysconfig/network # hdparm -t /dev/sdb <-- this is the redhat usb disk /dev/sdb: Timing buffered disk reads: 38 MB in 3.03 seconds = 12.55 MB/sec pi3:/etc/sysconfig/network # hdparm -t /dev/sda <--- dit is de snelle sandisk /dev/sda: Timing buffered disk reads: 88 MB in 3.05 seconds = 28.82 MB/sec </pre> e0fcff2dc2fcc83d30c20974170af6950a9d7037 0 543 2822 2799 2025-04-04T19:20:15Z Pvdm 2 wikitext text/x-wiki 20250404 <pre> # inxi -F System: Host: amd64 Kernel: 6.14.0-lp156.4.g37149af-default arch: x86_64 bits: 64 Console: pty pts/2 Distro: openSUSE Leap 15.6 Machine: Type: Desktop System: Gigabyte product: B550M K v: -CF serial: N/A Mobo: Gigabyte model: B550M K v: x.x serial: N/A BIOS: American Megatrends LLC. v: FD date: 03/22/2024 CPU: Info: 6-core model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP cache: L2: 3 MiB Speed (MHz): avg: 2506 min/max: 400/4465 cores: 1: 2367 2: 2367 3: 2367 4: 2367 5: 2367 6: 2367 7: 2367 8: 3443 9: 2967 10: 2367 11: 2367 12: 2367 Graphics: Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel Display: server: X.org v: 1.21.1.11 with: Xwayland v: 24.1.1 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1080~60Hz API: OpenGL v: 4.5 Mesa 23.3.4 renderer: llvmpipe (LLVM 17.0.6 256 bits) Audio: Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel API: ALSA v: k6.14.0-lp156.4.g37149af-default status: kernel-api Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth2 state: up speed: 1000 Mbps duplex: full mac: 10:ff:e0:7b:18:e2 RAID: Device-1: md1 type: mdraid level: raid-5 status: active size: 7.28 TiB report: 3/3 UUU Components: Online: 3: sdb 4: sdd1 5: sda Drives: Local Storage: total: raw: 11.03 TiB usable: 7.39 TiB used: 4.95 TiB (67.0%) ID-1: /dev/sda vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-2: /dev/sdb vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-3: /dev/sdc vendor: TCSunBow model: X3 120GB size: 111.79 GiB ID-4: /dev/sdd vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB Partition: ID-1: / size: 50 GiB used: 38.5 GiB (77.0%) fs: btrfs dev: /dev/sdc2 ID-2: /home size: 54.98 GiB used: 27.08 GiB (49.2%) fs: btrfs dev: /dev/sdc4 ID-3: /opt size: 50 GiB used: 38.5 GiB (77.0%) fs: btrfs dev: /dev/sdc2 ID-4: /var size: 50 GiB used: 38.5 GiB (77.0%) fs: btrfs dev: /dev/sdc2 Swap: ID-1: swap-1 type: partition size: 6.8 GiB used: 0 KiB (0.0%) dev: /dev/sdc3 Sensors: System Temperatures: cpu: 28.8 C mobo: 27.0 C gpu: amdgpu temp: 24.0 C Fan Speeds (RPM): N/A Info: Processes: 380 Uptime: 3h 58m Memory: available: 14.99 GiB used: 2.25 GiB (15.0%) Shell: Bash inxi: 3.3.27 </pre> 20240714 <pre> amd64:~ # inxi -C CPU: Info: 6-core model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP cache: L2: 3 MiB Speed (MHz): avg: 1046 min/max: 400/4464 cores: 1: 2989 2: 400 3: 400 4: 400 5: 400 6: 400 7: 2974 8: 400 9: 400 10: 400 11: 400 12: 2994 amd64:~ # inxi -F System: Host: amd64 Kernel: 6.9.7-lp155.2.ga5efffa-default arch: x86_64 bits: 64 Console: pty pts/2 Distro: openSUSE Leap 15.6 Machine: Type: Desktop System: Micro-Star product: MS-7B89 v: 1.0 serial: N/A Mobo: Micro-Star model: B450M MORTAR MAX (MS-7B89) v: 1.0 serial: K616819209 BIOS: American Megatrends LLC. v: 2.K0 date: 10/20/2023 CPU: Info: 6-core model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP cache: L2: 3 MiB Speed (MHz): avg: 616 min/max: 400/4464 cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 2993 12: 400 Graphics: Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel Display: server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1080~60Hz API: OpenGL v: 4.5 Mesa 23.3.4 renderer: llvmpipe (LLVM 17.0.6 256 bits) Audio: Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel Device-2: Focusrite-Novation Focusrite Scarlett 2i2 2nd Gen driver: snd-usb-audio type: USB API: ALSA v: k6.9.7-lp155.2.ga5efffa-default status: kernel-api Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth1 state: up speed: 1000 Mbps duplex: full mac: 2c:f0:5d:5b:ce:91 RAID: Device-1: md1 type: mdraid level: raid-5 status: active size: 7.28 TiB report: 3/3 UUU Components: Online: 3: sdb 4: sda1 5: sdc Drives: Local Storage: total: raw: 11.03 TiB usable: 7.39 TiB used: 4.96 TiB (67.1%) ID-1: /dev/sda vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-2: /dev/sdb vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-3: /dev/sdc vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-4: /dev/sdd vendor: TCSunBow model: X3 120GB size: 111.79 GiB Partition: ID-1: / size: 50 GiB used: 35.58 GiB (71.2%) fs: btrfs dev: /dev/sdd2 ID-2: /home size: 54.98 GiB used: 12.23 GiB (22.2%) fs: btrfs dev: /dev/sdd4 ID-3: /opt size: 50 GiB used: 35.58 GiB (71.2%) fs: btrfs dev: /dev/sdd2 ID-4: /var size: 50 GiB used: 35.58 GiB (71.2%) fs: btrfs dev: /dev/sdd2 Swap: ID-1: swap-1 type: partition size: 6.8 GiB used: 0 KiB (0.0%) dev: /dev/sdd3 ID-2: swap-2 type: file size: 9.54 GiB used: 0 KiB (0.0%) file: /data/swap/pvdmswapfile Sensors: System Temperatures: cpu: 29.0 C mobo: 33.0 C gpu: amdgpu temp: 27.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 1197 fan-3: 0 fan-4: 0 fan-5: 0 Info: Processes: 402 Uptime: 0h 39m Memory: available: 13.54 GiB used: 4.16 GiB (30.7%) Shell: Bash inxi: 3.3.27 </pre> old: <pre> amd64:~ # inxi -F System: Host: amd64 Kernel: 5.14.21-150400.24.21-default x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.4 Machine: Type: Desktop Mobo: Micro-Star model: B450M MORTAR MAX (MS-7B89) v: 1.0 serial: K616819209 BIOS: American Megatrends LLC. v: 2.H0 date: 07/27/2022 CPU: Info: 6-Core model: AMD Ryzen 5 5500 bits: 64 type: MT MCP cache: L2: 3 MiB Speed: 1413 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1413 2: 1359 3: 1421 4: 1397 5: 1397 6: 1397 7: 1397 8: 1401 9: 1408 10: 1397 11: 1396 12: 1396 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nvidia v: 470.141.03 Display: server: SUSE LINUX 1.20.3 driver: loaded: nvidia unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 21.2.4 Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.14.21-150400.24.21-default running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 IF: eth1 state: up speed: 1000 Mbps duplex: full mac: 2c:f0:5d:5b:ce:91 RAID: Device-1: md1 type: mdraid level: raid-5 status: active size: 7.28 TiB report: 3/3 UUU Components: Online: 3: sdc1 4: sdb1 5: sdd1 Drives: Local Storage: total: raw: 11.03 TiB usable: 7.39 TiB used: 4.9 TiB (66.3%) ID-1: /dev/sda vendor: TCSunBow model: X3 120GB size: 111.79 GiB ID-2: /dev/sdb vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-3: /dev/sdc vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB ID-4: /dev/sdd vendor: Western Digital model: WD40EFAX-68JH4N0 size: 3.64 TiB Partition: ID-1: / size: 50 GiB used: 46.05 GiB (92.1%) fs: btrfs dev: /dev/sda2 ID-2: /home size: 54.98 GiB used: 6.58 GiB (12.0%) fs: btrfs dev: /dev/sda4 ID-3: /opt size: 50 GiB used: 46.05 GiB (92.1%) fs: btrfs dev: /dev/sda2 ID-4: /tmp size: 50 GiB used: 46.05 GiB (92.1%) fs: btrfs dev: /dev/sda2 ID-5: /var size: 50 GiB used: 46.05 GiB (92.1%) fs: btrfs dev: /dev/sda2 Swap: ID-1: swap-1 type: partition size: 6.8 GiB used: 0 KiB (0.0%) dev: /dev/sda3 ID-2: swap-2 type: file size: 9.54 GiB used: 0 KiB (0.0%) file: /data/swap/pvdmswapfile Sensors: System Temperatures: cpu: 26.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 1566 fan-3: 0 fan-4: 0 fan-5: 0 Info: Processes: 310 Uptime: 0h 44m Memory: 15.5 GiB used: 1.62 GiB (10.5%) Shell: Bash inxi: 3.3.07 OLD:======================= Base Board Information Manufacturer: ASRock Product Name: FM2A88M Pro3+ Version: Serial Number: M80-A3022300574 Processor Information Socket Designation: CPUSocket Type: Central Processor Family: A-Series Manufacturer: AMD ID: 31 0F 61 00 FF FB 8B 17 Signature: Family 21, Model 19, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Multi-threading) Version: AMD A8-6600K APU with Radeon(tm) HD Graphics Voltage: 1.3 V External Clock: 100 MHz Max Speed: 3900 MHz Current Speed: 3900 MHz Status: Populated, Enabled Upgrade: Socket FM2 L1 Cache Handle: 0x0008 L2 Cache Handle: 0x0009 L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 4 Core Enabled: 4 Thread Count: 4 Characteristics: 64-bit capable 0a7b6a2bc9e8935ba4ad4a752319783cd63c7460 0 2 2823 2817 2025-04-06T14:07:56Z Pvdm 2 wikitext text/x-wiki *[[rsync root volume to new harddisk]] *[[enable wifi after suspend-resume]] *[[edit PDF metadata]] *[[change root's theme]] *[[swap file on BTRFS]] *[[chrome options]] *[[fix bash history]] *[[How to send email from command line in fixed font]] *[[update etherpad]] *[[rootvg won't resize]] *[[x11 forwarding for sudo users]] *[[chromecast op linux]] *[[AIX cheatsheet]] *[[linux algemeen]] *[[SOX audio examples]] *[[sort installed rpms by size]] *[[view progress of dd]] *[[dealing with spaces in filenames]] *[[POSTFIX]] *[[How to backup your disk with dd]] *[[How to make a webcam page with Apache on Linux]] *[[How to make Audacity work with ALSA]] *[[Reinstalling GRUB after Windows install]] *[[Make .par files work in KDE]] *[[Keyboard setting for diacritical characters]] *[[How to make a .iso file from your CD or DVD]] *[[How to find duplicate files BY CONTENT!!]] *[[How to clone or copy your harddisk over the network]] *[[How to connect to server on strange port, or when you're behind a firewall]] *[[How to find information about a host or webserver]] *[[How to make a virtualBox window seamless]] *[[Using bridged networking in VirtualBox]] *[[Mounting remote directories using FUSE and sshfs on openSUSE]] *[[Using x2x to connect two computers and their screens with one mouse and keyboard]] *[[Convert an AVCHD / MTS file to MP4 using ffmpeg]] *[[How to restore MBR on harddisk]] *[[How to automatically log in to remote ssh servers using public/private keypair]] *[[How to make an encrypted directory]] *[[How to send mail via telnet to a server using SMTP commands]] *[[How to test network speed]] *[[How to convert an existing ext3 filesystem to ext4]] *[[How to make a dump of a website]] *[[Linux performance monitoring]] *[[How to make a shell fork bomb]] *[[How to resque a hanging linux]] *[[Script to check and restart a process]] *[[Enlarge disks by removing reserve space on ext2/3/4]] *[[SSH filesystem]] *[[Using GRUB to boot multiple operating systems, the correct way]] *[[iptables for dummies]] *[[Convert .pcd (PhotoCD) files]] 2640dcc35e50d596ab4a5865f9e4c90003addb8e 0 622 2824 2025-04-06T14:08:53Z Pvdm 2 Created page with " # rsync -aAXvx --progress --exclude='.snapshots/' / [mountpoint of new harddisk]" wikitext text/x-wiki # rsync -aAXvx --progress --exclude='.snapshots/' / [mountpoint of new harddisk] 07aeda5ff4dcc746af87d20d26a169914e3d5dbb 0 551 2825 2276 2025-05-06T15:38:01Z Pvdm 2 wikitext text/x-wiki <pre> FAQ - Digital compact cass recorder GENERAL INFORMATION . 900 Series ''Digital Convenience'' DCC recorder . Direct digital recording . Plays also Compact Cassettes . Full 18-bit system . Turbo drive . Title recording . Microphone input . ''System Intelligence'' bus AUDIO TAPE DECK DIGITAL DCC (playback) Sample frequencies: 44.1 kHz, Wow and Flutter : Quartz Crystal Precision DIGITAL DCC (recording, line in) Sample frequencies: 44.1 kHz, DIGITAL DCC (recording, digital/optical in) Sample frequencies: 32 kHz (satellite Tuner e.g.) 44.1 kHz (CD) 48 kHz Perfect digital recording AUDIO/SOUND DIGITAL DCC (playback) Frequency range : 20Hz-20kHz Amplitude linearity : � 0.05 dB S/N ratio (A-weighted): � 105 dB (1 kHz) Dynamic range : � 100 dB (1 kHz) THD+N : � 90 dB (10 kHz) Channel Separation : � 110 dB (1 kHz) DIGITAL DCC (recording, line in) Frequency range : 20Hz-20kHz Amplitude linearity : � 0.1 dB S/N ratio (A-weighted): � 100 dB (1 kHz) Dynamic range : � 92 dB (1 kHz) THD+N : � 85 dB (1 kHz) Channel Separation : � 100 dB (1 kHz) ANALOGUE CASSETTE (playback only) Frequency range : 40Hz-16kHz (CrO2) S/N ratio (A-weighted): 55 dB (CrO2) Dolby B/C : Improvement B: 10 dB Improvement C: 18 dB Signal also supplied to digital outputs Headphone amplifier performance . Load Impedance Range: 32-600 Ohm . Output impedance : 170 Ohm . Output voltage (L+R): Max. 5V Rms . Frequency range : 20-20 kHz Microphone . Microphone impedance Range : 200-2000 Ohm OPERATION/CONTROLS . Remote control RC-5, 20 keys supplied CONNECTIONS Inputs: Analogue : impedance 50 K ohm Digital Coaxial: acc. to IEC 958 Digital optical: TOSLINK Outputs: Analogue : 2V ms Digital Coaxial: acc. to IEC 958 MISCELLANEOUS Dimensions (wxhxd) : 435x90x300 mm Display : 14 characters FTD Material/Finish : Metal and polystyrene Mechanism : 2 motor metal deck RC socket : ESI bus, 2x cinch Tape-speed level : 4.76 cm/sec FREQUENTLY ASKED QUESTIONS PLAYBACK: DCC cassettes Problem: DCC cassettes causing faults (a.o. drop outs, tape salad, clean head). Cause : DCC cassettes outside specification. REMARKS : The used DCC cassette is not according the DCC specification and so NOT released by Philips. (e.g. some of Maxell and Fuji cassettes) It is recommended to use released Philips DCC cassettes only. PLAYBACK: Skipping small part of music Problem: Skipping small part of music of pre-recorded DCC-cassettes after track search Cause : Repositioning problem due to high fast wind/rewind speed. REMARKS : After track search command the DCC does not start exactly at the beginning of a track. First approx. 500 msec. of track are not played back. This problem does not occur when DCC-cassette is played-back normally. This deviation is dependant on the position of the tape; via the reel-tacho signals the movement of the reel is measured not the tape. To reduce this error a compensation is done, based on an average required repositioning within � 0.5 sec. Only in the minus area this short jump could be noticed. This problem cannot be solved. TRACK AND TIME: REMaining time Problem: REMaining time indication is not reliable. Cause : Calculation of remaining time by DCC recorder REMARKS : The DCC recorder starts with defining an estimated total remaining time. After that it calculates the elapsed time by reading total time information of played back tracks. The remaining time left on tape is the estimated playing time of the cassette minus the elapsed time. The remaining time might have a tolerance of about 1 minute. So it might happen that for instance the display shows 'REM TIME 5:38, and yet a music piece of about 4:14 will not fit. TRACK AND TIME: Track and Time information is erased Problem: Track and Time information is erased when adding text information. Cause : Not correct initialized cassette. REMARKS : Sometimes track number and time information is erased when recording text information. When using RENUMBER to reconstruct the track numbering again the missing time information will be misinterpreted as tape end and tape direction is reversed, while renumbering continues on side B. OPERATING: "DUBBING ACTIVE" Problem: Message 'DUBBING ACTIVE' on display of DC951. Cause : Via presets like: source CD and CD SYNCHRO ON the reference for CD dubbing is defined. REMARKS : After actuating REC SELECT/PAUSE key the DCC951 is looking for its preference entry in the Philips 900 series system, with correct ESI BUS connections. When the presets are set to source CD and CD SYNCHRO ON the set is waiting for acknowledge command from CD player. In case other keys are pressed in the meantime the message 'CD DUBBING ACTIVE' is shown as operating error message. If ESI BUS is not connected in the right way the message 'NO CD SYNCHRO' is shown. NOTE: CD SYNCHRO mode can be changed with the PRESETS function as follows: - press PRESETS - press RECORD - by pressing 'wind' or 'rewind' the presetted CD SYNCHRO mode can be switched ON or OFF - press PRESETS to store settings. Only valid for DCC951. OPERATING: AUTO STOP mode Problem: DCC recorder does not stop after last recording when selected AUTO STOP mode. Cause : Auto stop function is wrongly interpreted by user. REMARKS : With the PRESETS function the playback function can be set as soon as a cassette is inserted. With playback set at AUTO PLAY, playback will always be started automatically as soon as the tray has been closed (and cassette is inserted) by pushing the tray by hand or the POWER has been switched ON. With playback set at AUTO STOP, playback will not start automatically. NOTE: To find last recording user should use APPEND to search for the end of the last recording (which was marked when STOP was pressed during recording). APP > or APP < appears. When this position has been found the last 10 seconds will be played back (APPEND PLAY), after which the RECORD PAUSE (REC-P) mode is entered. OPERATING: NO CD SYNCHRO desired Problem: NO CD SYNCHRO desired by user of DCC951. Cause : Function CD SYNCHRO ON is selected in preset. REMARKS : When CD SYNCHRO option is not required by user, or not via ESI BUS connected with other sets from the Philips 900 series system, it should be switched off. This can be done as follows: - press PRESETS - press RECORD - press WIND or REWIND to switch to CD SYNCHRO OFF - press PRESETS to store presets. To use CD SYNCHRO ON presets must be changed by applying above mentioned procedure again and the ESI BUS should be proper connected to other sets in the Philips 900 series system. Only valid for DCC951. OPERATING: Operation of source selector Problem: Operation of source selector is not clear. Cause : IFU does not explain selection of source very clear. REMARKS : After installation of the DCC recorder all input sources should be selected via source preset. This is done as follows: - Press PRESET - By pressing REC SELECT/PAUSE the default CD is indicated on display. By pressing NEXT key the cable connection made with CD player can be selected. By pressing again REC SELECT/PAUSE the next input source (tuner etc) can be selected. Every time again the applied cable connection with source can be selected via the NEXT key. - When all sources (to be recorded from) via REC SELECT/PAUSE and NEXT are selected these presettings are stored by pressing PRESET. Making a recording from one of the sources the latest used source (this setting is also stored by the set) is selected. If another source should be selected this is done as follows: - Press REC SELECT/PAUSE, the default source is already indicated on display (except Microphone). - By pressing REC SELECT/PAUSE again next source is selected. - Subsequently pressing REC SELECT/PAUSE gives the other available sources. Sequence of source selection is CD TUNER AUX1 AUX2 CD TUNER, etc. In case microphone socket has been connected this input source is selected automatically. NOTE: In case a digital recording will be made from CD or AUX as source and no digital connection is made the message: 'CHECK DIG IN' is displayed and one should reconnect digital cable from recorder to source. For more detailed information See the Instructions for Use. A quick reference card for ease of operating is made available: For DCC730 with service code 4822 725 22612 For DCC951 with service code 4822 725 22611 These reference cards contain clear pictographs to operate the DCC recorder. OPERATING: Operate DCC recorder Problem: It is difficult to operate DCC recorde. Cause : DCC recorder is software controlled (play back = CD similar). REMARKS : Correct understandings of the user-recorded tape formats and markers will help customers to make full use of the benefits of the DCC recorder. See also newsletter 63.01. For ease of operationg a quick reference card is made available: For DCC730 with service code 4822 725 22612 For DCC951 with service code 4822 725 22611 These reference cards contain clear pictograms to operate the DCC recorder for every mode. OPERATING: Renumbering Problem: Renumbering not possible when making a new recording at specific location. Cause : In User format is RENUMBER not possible. REMARKS : Before recording first initializing of the tape has to be performed. See also newsletter item 63.01 OPERATING: Music passages are lost Problem: Music passages are lost after renumbering. Cause : 'CONTINUE B' (REVERSE) and 'GO TO START A' (STOP) marker cannot be erased. REMARKS : Markers which are recorded on the tape, control the set in play back mode. This means that in PLAY mode all information recorded on tape behind the 'Continue B' marker or 'Go to Start A' marker is skipped. The recordings behind those markers can only be reached by winding over that marker. OPERATING: Track numbering Problem: Track numbering does not start at number 1 when recording side B. Cause : Per default single Album format is defined. REMARKS : Track numbering starts at side A (when AUTO EDIT ON) directly after the LEAD-IN area with number 1. Track numbering is automatically incremented when recording new tracks and continues on side B. In other words the DCC tape is seen as one single album where one may select a particular track, and it does not matter whether the required track is on side A or B of the tape. If user wants to start track numbering with track 1 on side B to obtain e.g. a dual Album, EDIT function must be performed. When in REC-PAUSE mode: - - press EDIT key to enter the edit mode - select required EDIT function by pressing EDIT several times - press RECORD key to actually edit the tape. Next edit functions are available: - - START NEW SIDE: to start track numbering on side B with track number 1. When restarting of track numbering is required, user must search for last recording on side A, record START NEW SIDE indication. - CONTINUE B: track numbering is continued at side B. - GO TO START A: marks the position where the deck should start winding to the beginning of side A and stop. RECORDING: Analog level Problem: Analog level cannot be reduced until zero using REC LEVEL control. Cause : No analog fade in/out option available. REMARKS : Recording level control is not meant to obtain fade in/out effects for own analog recordings. Typical fade in/out feature is not available on DCC sets. Analog recording level control is meant to be used for adapting input level for analog signals. To obtain real fade in/out effects an audio mixing unit (e.g. SBC5370), connected to AUX - ANALOG IN, should be applied. RECORDING: Clicks are audible Problem: Clicks are audible when interrupting recording with REC PAUSE. Cause : Difference between digital mute (-110dB) and analog silence (>-30dB) can be recognized as click being recorded. REMARKS : By mixing different titles (from e.g. various Vinyl Records) clicks are audible between the analog silence signal of the vinyl recording and the interrupting of the recording with REC PAUSE (digital mute). It is this difference in level between the analog silence and the digital mute (system detects a sudden increase of level) that the DCC recorder records, and is audible as a click during play back at high volume level. RECORDING: Old recordings remain Problem: Parts of old recordings remain after overwriting existing recordings. Cause : Cassette is not initialized correctly before overwriting. REMARKS : When a CD-synchro recording is made on a DCC-tape which was already recorded in the past, the set switches at the estimated end from side A to side B. When playing back this part of the tape first the 'new' music is heard followed by the 'old' music until end of side A and in the beginning of side B. This problem can be prevented by renumbering the tape. NOTE: To overwrite a previous recorded DCC tape press REWIND key more than 0.5 second (set must be in STOP mode). Tape is rewound to the beginning of the tape. By pressing REC SELECT/PAUSE key the LEAD IN portion of about 10 seconds is recorded. Afterwards the set goes to Record Pause mode. When pressing RECORD the recording starts and tape will be completely overwritten. Set 'sees' tape as being new. To record in the middle of an existing track (recording on a specific location) first the location should be searched, than (in STOP mode) press subsequently REC SELECT/PAUSE and RECORD. RECORDING: Track numbering Problem: Track numbering DCC does not match with the track numbering of the source (e.g. when digital copying a Compact Disc) Cause : Track number is automatically increased at end of side A with CD SYNCHRO OFF. REMARKS : At end of side A a CONTINUE B marker is recorded. The DCC standard requires a new track number at the start of side B. This marker is not on the CD, so all recordings from side B have a track number (CD track number + 1). RECORDING: Track numbering Problem: Track numbering does not match with the track numbering of the source (e.g. when analog copying a Compact Disc). Cause : Track number is recorded after an analog silence (signal level below -60dB) for more than 3 seconds and track number is automatically increased at end of side A with CD SYNCHRO OFF. REMARKS : - In AUTO EDIT ON mode a new track number will be written after every silence for more than 3 seconds, where 'silence' is defined as an analog signal level below -60dB. It might happen that a source (Compact Disc) has music pauses for more than 3 seconds within one music number, or pauses between tracks are shorter than 3 seconds. User may edit the track numbering afterwards by CONNECTing or SPLITting TRACKS. By connecting tracks the current and next 'pause' track will be connected and later on recognized as one track. During this action the DCC recorder will erase the START indication of that 'pause' track. By splitting tracks the current track will be split up in two successive tracks. - DCC standard requires a new track number at the start of side B. (See also problem "RECORDING: Writing markers in AUDIO EDIT") NOTE: When tracks have been connected or splitted also a RENUMBER action is necessary to ensure a correct track number sequence. RECORDING: Writing markers in AUTO EDIT Problem: Writing markers in AUTO EDIT mode after more than 3 seconds of silence. Cause : IFU mentions 3 seconds of silence. REMARKS : In AUTO EDIT ON mode the DCC recorder writes new track numbers on the tape when silences (signal level below -60dB) of more than 3 seconds are detected during recording from ANALOG input. The signal level of the source must be below -60dB before DCC system recognizes a music pause. It might happen that during fading out of music, the user perceives a silence but that signal level is not dropped below -60dB. In this case the music pause seems to be much longer than 3 seconds. Note: In AUTO EDIT OFF the DCC recorder will not perform automatic track increment when recording from analog sources. AUTO EDIT is always set to ON when a digital source is connected (via digital sockets). RECORDING: Microphone recording input Problem: Microphone recording input is only Mono Cause : Only Mono microphone pre-amplifier designed. REMARKS : When microphone is connected, the DCC set automatically selects the MONO microphone input. Recording via another source is not possible as long as microphone is connected. When Stereo recording via microphone is required it is recommended to connect microphone(s) to an audio mixing unit (e.g. SBC5370) which must be connected to AUX, ANALOG IN. PLAYBACK: De-emphasis Problem: De-emphasis in DCC player is not functioning after making a digital copy of a Compact Disc. Cause : In PLAYBACK mode the DCC recorder switches de-emphasis ON or OFF dependant to the contents of the system information (SYSINFO). REMARKS : De-emphasis of a DCC recording is only activated in PLAYBACK mode if concerned bit in sysinfo is switched on. This flag is set during recording from digital input. This information is sent from the CD player to the DCC recorder. In play back the DCC recorder switches de-emphasis on or off dependant of the flag setting in sysinfo. Recording via analog input will not set the de-emphasis flag. This is already performed in the CD player via the information in the SUBCODE. Manually on/off switching of de-emphasis by user is not possible. PLAYBACK: CLEAN HEAD Problem: CLEAN HEAD indication Cause : Contaminated head. REMARKS : The special design of DCC-head makes it sensitive for contamination, especially when low quality ACC tape (Fe tape) is used. The applied DCC tape consists of high quality chrome tape, which will not contaminate the head. In order to ensure high quality recording the warning of the CLEAN HEAD indication is displayed according following criteria: - about 8 hours of total playing back time of ACC tape. - 2 channels or more on DCC tape not detected by DCC head for more than 3 seconds. please notice: In case CLEAN HEAD indication was caused by a temporarily bad HEAD-TAPE contact, the message will disappear after pressing the 'TIME' or 'TEXT' key. </pre> 915cd70381adde66cff8f0908e65dc5afc40e241 0 612 2828 2827 2025-05-14T08:24:42Z Pvdm 2 wikitext text/x-wiki # badblocks -e 10 -s -w /dev/mmcblk0 -e max bad block count<br> Specify a maximum number of bad blocks before aborting the test. The default is 0, meaning the test will continue until the end of the test range is reached. -s show progress -w use write mode -n Use non-destructive read-write mode.<br> By default only a non-destructive read-only test is done. This option must not be combined with the -w option, as they are mutually exclusive. Pass completed, X bad blocks found (R/W/C errors) The three numbers in the parentheses correspond to: *Read errors: Errors encountered while reading from the disk. *Write errors: Errors encountered while writing to the disk. *Corruption (Compare) errors: Errors where the data read back from the disk does not match what was written (i.e., data corruption detected during verification) # smartctl -t long /dev/device remember no smart on sd cards c6b277917462b00915dcd59ff37d2a3b70f58bc8 0 1 2829 2793 2025-06-17T06:43:19Z Pvdm 2 /* Categories: */ wikitext text/x-wiki [[File:tux-blink.gif|right|penguin]] == Categories: == *[[ace]] *[[Android]] *[[ansible]] *[[Apache en HTML]] *[[Audio]] *[[awk]] *[[Bash fun]] *[[Bash pitfalls]] *[[Books]] *[[btrfs]] *[[Commodore64]] *[[Convert an AVCHD / MTS file to MP4 using ffmpeg|Ffmpeg]] *[[CUPS]] *[[exiftool]] *[[find]] *[[Gezondheid]] *[[GRUB]] *[[Grub2: boot USB from GRUB prompt]] *[[Image manipulation (The Gimp, DigiKam)]] *[[KDE4]] *[[KVM]] *[[Linux and hardware]] *[[Linux commandline tips]] *[[Linux commandline tips 2]] *[[Linux commandline tips 3]] *[[Linux commandline tips 4]] *[[Linux general]] *[[MediaWiki]] *[[MySQL]] *[[MythTV]] *[[Nagios]] *[[nmap]] *[[Novell related]] *[[OCR]] *[[openSUSE specific]] *[[Other general]] *[[PipeWire Quick Reference Guide]] *[[Raspberry Pi]] *[[Sound (Audacity)]] *[[SOX audio tool Quick Reference Guide]] *[[Systems]] *[[Video (Kino, dvgrab, OpenShot, KdeNlive)]] *[[VirtualBox]] *[[Vi tips]] *[[Wine]] *[[XBMC]] *[[Xorg]] *[[yt-dlp]] *[[Zypper tips]] 96f23c91e897279bc1d6bc75d50d1a767fc58c27 0 623 2832 2831 2025-06-17T06:58:29Z Pvdm 2 wikitext text/x-wiki To fix the date time on the pixel 6a photo and video files, use for photos: # exiftool '-FileName<DateTimeOriginal' -d '%Y%m%d_%H%M%S%%-c.%%e' *.jpg and for video files: (NOT ENTIRELY CORRECT NEEDS UPDATING!!) # exiftool '-FileName<FileModifyDate' -d '%Y%m%d_%H%M%S%%-c.%%e' *.mp4 e97d2cb0b79c54731442a2259ce4cb75a8050f14 0 434 2833 2788 2025-06-21T19:44:39Z Pvdm 2 wikitext text/x-wiki *[[Revox B215]] *[[installing audio plugins]] *[[Use yt-dlp the correct way for music files]] *[[Use yt-dlp with subtitles for video files]] *[[Use METAFLAC to edit Flac Tags]] *[[use NAB test tape to calibrate IEC deck and vice versa]] *[[pulseaudio settings for audiophiles]] *[[Otari Mx-55 N-M]] *[[24bit vs 16bit, the myth exploded!]] *[[Athana PF-212 Bulk Eraser]] *[[cm6631a]] *[[check soundcard settings: bitrate]] *[[vlc tips & tricks]] *[[lagers]] *[[jazz]] *[[DCC chips]] *[[DCC FAQ]] *[[DCC history]] *[[DCC tapes]] *[[Philips DCC170]] *[[Philips DCC600]] *[[Philips DCC900]] *[[Philips DCC951]] *[[Philips FW68]] *[[Technics RS-BX501]] *[[Technics SL-P777]] *[[BASF tape formulas]] *[[BASF Cassette history]] *[[Doormeten van een transistor]] *[[My setup]] *[[Quadrophonic or DTS surround sound]] *[[muziek verlanglijstje]] *[[Teac A-3440]] *[[Tascam history]] *[[Studer A80 history]] *[[Dolby NR]] *[[dbx]] *[[de dB]] *[[Reel to reel tapes info]] *[[cleaning contacts - contact spray]] *[[knosti liquid]] *[[DVDA authoring]] *[[Reference Tapes - Calibration]] *[[plakkende tapes afspelen]] *[[identificatie van reel to reel tapes aan de hand van de aanloopstrook]] *[[tape reference level]] *[[Flux Level Standards]] *[[Revox PR99 reference level]] *[[Revox PR99 history]] *[[Velleman PCSGU250]] *[[Degaussing]] *[[NAB vs. IEC]] *[[Technics 1500 - 1700]] b589dfe9180785e3637b16faeec63f2832d4782d 6 625 2845 2025-06-21T20:18:42Z Pvdm 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 624 2846 2844 2025-06-21T20:19:22Z Pvdm 2 wikitext text/x-wiki De Revox B215 is een cassettedeck die van 1985 tot ongeveer 1990 door Studer werd geproduceerd . Een professionele versie met een andere bedieningsindeling en audiopadelektronica werd gelijktijdig geproduceerd als de Studer A721 . Een later verbeterde versie werd op de markt gebracht als de Revox B215S . Omdat hij duurder was in vergelijking met andere consumentenmodellen en uitzonderlijk goede mechanische prestaties en duurzaamheid had, werd de B215 voornamelijk gebruikt door professionele klanten: radiostations, opnamestudio's en realtime [ a ] cassetteduplicators. [[File:Revox B215 cassette deck.jpg|Revox B215 cassette deck]] De B215 maakte gebruik van een beproefd, betrouwbaar bandtransport met vier motoren, afgeleid van het eerdere model B710. De B215 onderscheidde zich van de B710 en concurrerende decks uit die tijd door een ongebruikelijk, computerachtig bedieningspaneel en uitgebreide automatisering, uitgevoerd door drie Philips- microcontrollers . Het deck was uitgerust met automatische bandkalibratie, microcontroller-ondersteunde instelling van opnameniveaus en niet-vluchtig geheugen . De objectieve, onafhankelijk gemeten en geverifieerde specificaties van de Revox evenaarden of overtroffen die van de beste concurrerende decks; vergelijkende tests plaatsten de B215 op hetzelfde niveau als de Nakamichi Dragon en boven de vlaggenschipmodellen van ASC, [ b ] Harman Kardon , Tandberg of TEAC . Recensenten prezen de Revox om zijn voorbeeldige mechanische kwaliteit en de verwachte duurzaamheid van zijn tapetransport, maar bekritiseerden hem om een ​​lager dan verwacht dynamisch bereik en tekortkomingen in bruikbaarheid . =Ontwikkeling en productie= Studer AG , een particuliere Zwitserse fabrikant van professionele audioapparatuur, begon eind jaren zeventig met de ontwikkeling van high-fidelity cassetterecorders . Willi Studer aarzelde om te diversifiëren naar de zeer concurrerende markt voor cassettedecks; gedurende het grootste deel van het decennium beperkte de ervaring van het bedrijf op het gebied van cassettetechnologie zich tot betrouwbare, maar low-fidelity apparatuur voor in het klaslokaal. [ 1 ] [ 2 ] De daling van de verkoop van spoelenrecorders , het commerciële succes van Nakamichi en de " designermodellen " van Bang & Olufsen , in combinatie met druk van binnenuit het bedrijf, overtuigden Studer er echter van om te investeren in het cassetteformaat. [ 2 ] Marino Ludwig, ontwerper van de Revox B77 spoelenrecorder, [ 3 ] onderzocht de beste cassettedecks op de markt en adviseerde Studer over een handelwijze. [ 2 ] Studer ging akkoord met het voorstel en benoemde Ludwig tot hoofd van het cassetteproject, op voorwaarde dat de reputatie van de merken Studer en Revox op geen enkele manier in gevaar zou worden gebracht. [ 2 ] In september 1980 presenteerde Studer AG zijn eerste cassettedeck, de Revox B710 ; in 1981 werd deze vervangen door de bijna identieke Revox B710 MKII, die Dolby C- ruisonderdrukking toevoegde. In 1982 introduceerde het bedrijf een professionele versie, de Studer A710, uitgerust met gebalanceerde ingangen en uitgangen . [ 4 ] In de Verenigde Staten kostte de B710 MKII $ 1995, [ 5 ] meer dan de rivaal Nakamichi ZX7 ($ 1250), maar minder dan het vlaggenschip Nakamichi 1000ZXL ($ 3800 voor de basisversie, [ 6 ] of $ 6000 voor de "gelimiteerde" editie. [ 7 ] ) De B710 met drie koppen werd ontworpen en gebouwd volgens de normen van professionele reel-to-reel decks; zelfs het frontpaneel en de bedieningselementen werden geleend van de B77-recorder. [ 2 ] De B710 onderscheidde zich van de concurrentie doordat hij een echt viermotorig direct-drive tapetransport had : elk van de twee capstans en de twee spoelen werden aangedreven door hun eigen elektromotor zonder tussenliggende riemen , tandwielen of meelooprollen . [ 2 ] Er waren geen remblokken , riemen, katrollen of tandwielen in het hele transport; zelfs de tapeteller werd aangedreven door een opto-elektronische encoder op de spoelmotoren. Mechanisch gescheiden opname- en afspeelkoppen waren elk instelbaar, maar er was geen voor de gebruiker toegankelijke azimutregeling . De B710 was mechanisch solide, maar miste functionaliteit; belangrijker nog, het deck miste voor de gebruiker toegankelijke tapekalibratieregelaars. Over het algemeen was het ontwerp zeer conservatief. [ 1 ] Marino Ludwig schreef dat de ontwikkeling samenviel met een stortvloed aan nieuwe functies ( Duits : der Flut von Neuheiten ) geïntroduceerd door de Japanners, en slechts een paar, zoals automatische tapetypeherkenning, konden binnen de deadline worden geïmplementeerd . [ 1 ] Niet-geteste nieuwigheden die het product in gevaar konden brengen, zoals dynamische voorspanning , werden van begin af aan afgewezen. [ 1 ] In 1984 ontwierpen Ludwig en Meinrad Liebert een opvolger van de B710, de B215. [ 2 ] De eerste pre-productiebatch werd eind 1984 geassembleerd; de eerste productiedecks werden begin 1985 naar dealers verzonden. [ 8 ] Een professionele afgeleide, de Studer A721, leek sterk op de B215, maar was uitgerust met gebalanceerde in- en uitgangen en traditionele draaiknoppen voor het volume in plaats van omhoog-omlaagknoppen. De pers plaatste de B215 op gelijke voet met de beste concurrerende decks, en beoordeelde de geluidskwaliteit als hoog, of bijna zo hoog als die van het nieuwe referentiedeck - de Nakamichi Dragon . In de Verenigde Staten kostte de B215 aanvankelijk 'slechts' $ 1390, [ 9 ] lager dan zowel de B710 als de Dragon. 'Betaalbare' prijzen en robuust transport maakten de B215 het deck bij uitstek voor real-time [ a ] ​​cassetteduplicators; Zo exploiteerde het in Vermont gevestigde Revolution Audio in april 1986 een vloot van 200 B215's, 24 uur per dag, vijf dagen per week, en was het van plan er nog eens 200 aan te schaffen. [ 10 ] Het Duitse audiotijdschrift gebruikte een stapel van tien B215's om zijn eigen testcassettes te dupliceren. [ 11 ] Ludwig schreef dat de prijsdaling de kostenbesparingen weerspiegelde die bereikt werden door het gebruik van grotere printplaten en geautomatiseerde assemblage . [ 12 ] De introductie van de B215 viel ook samen met een recordlage wisselkoers van de Zwitserse frank ten opzichte van de Amerikaanse dollar, die in februari en maart 1985 een historisch dieptepunt bereikte. [ 13 ] Vervolgens steeg de wisselkoers van de Zwitserse dollar gestaag, [ 13 ] en zo ook de Revox-prijzen in Noord-Amerika. In 1989 kostte de B215 $ 2400, [ 14 ] en in 1991 $ 2600. [ 15 ] De verbeterde, cosmetisch herontworpen B215S, geïntroduceerd in 1989, kostte $ 2800–$ 2900 [ 14 ] [ 15 ] — meer dan de Dragon, en drie tot vier keer meer dan hedendaagse vlaggenschipdecks van Onkyo , Pioneer of Sony . [ 15 ] Tegen die tijd was Willy Studer met pensioen; in 1990 verkocht hij het bedrijf en in 1994 werd het een dochteronderneming van Harman International . [ 16 ] De nieuwe cassettedecks van het merk Revox die onder Harman-management werden verkocht, de consumenten-H11 en de professionele C115, [ 17 ] waren in feite omgedoopte Philips FC-60 / Marantz SD-60-modellen en hadden niets gemeen met de Revox-modellen uit het verleden. [ 18 ] Klassieke vlaggenschipdecks uit de jaren tachtig, zoals de B215, de Dragon of de Tandberg 3014, werden niet meer geproduceerd zonder vervanging. [ 19 ] Verdere verbeteringen van het cassettegeluid vereisten, indien überhaupt mogelijk, aanzienlijke investeringen in onderzoek, maar de bedrijfsmiddelen waren al toegewezen aan digitaal. [ 19 ] =Ontwerp en werking= ===Uiterlijk en ergonomie=== Achteraanzicht van het bandtransport. Twee bronzen vliegwielen onderin zijn rotors van de capstanmotor. Daarboven bevindt zich de solenoïde die het kopsubchassis (midden) optilt en de bijbehorende demper (links, zwart). De B215 is, net als alle Revoxes uit de B-serie, groter dan het typische hifi-onderdeel uit die tijd. [ 20 ] De behuizing meet 45 bij 15 bij 33 centimeter (17,7 inch × 5,9 inch × 13,0 inch) [ 20 ] en is een standaard Studer geperste stalen kast met twee interne verstevigingsrails die het tapetransport dragen. [ 21 ] [ 22 ] Het ontwerp van het voorpaneel volgt de stijl van de B200-serie, die in 1984 werd geïntroduceerd met de release van de B225 cd-speler. [ 23 ] De bedieningselementen voor het tapetransport en de opnamemodus, die op de bovenste aluminium strip zijn geplaatst, zijn visueel gescheiden van secundaire knoppen. [ 23 ] Het laden van de cassette in een open transport gebeurt in twee bewegingen: eerst wordt de bovenrand van een cassette ingebracht, vervolgens wordt de onderkant van de cassette ingedrukt totdat deze vastklikt. [ 21 ] Dit levert geen probleem op bij dagelijks gebruik. [ 21 ] Open tapetransport is minder gevoelig voor azimutscheefstand dan typische gesloten-dekseltransporten, en vereenvoudigt routinematige reiniging en demagnetisatie. [ 21 ] [ 24 ] De opnameniveaus, de opnamebalans en het hoofdtelefoonvolume worden elektronisch ingesteld met behulp van omhoog-/omlaagknoppen. [ 25 ] [ 26 ] Er zijn geen microfooningangen; ontwerpers achtten die overbodig voor een consumentenproduct. [ 22 ] De markering op het paneel is volgens recensenten van het tijdschrift Audio (USA) exemplarisch: zwarte letters op geborsteld aluminium en witte letters op donkergrijs plastic zijn groot genoeg en vanuit elke kijkhoek gemakkelijk leesbaar. [ 27 ] Het belangrijkste lcd-scherm met achtergrondverlichting is daarentegen te klein, te donker en te moeilijk leesbaar. [ 28 ] [ 24 ] Een ander gebrek aan bruikbaarheid is de afwezigheid van controlelampjes op het voorpaneel; zelfs het kritieke rode lampje 'Record On' ontbreekt (het werd later toegevoegd aan de Studer A721, maar niet aan de B215). [ 28 ] Door deze eigenaardigheden is het lastig om de Revox in een donkere kamer te gebruiken. [ 28 ] Recensenten merkten ook op dat het gebruik van digitale bedieningsknoppen in plaats van draaipotentiometers over het algemeen onhandig was [ 24 ] ( dit laatste kwam weer terug op de Studer A721, maar niet op de Revox-decks). ===Bandtransport=== Typisch dubbel-capstan-bandtransport uit de jaren 80 gebruikte alleen directe aandrijving voor de voorste (trekkende) capstan; [ 29 ] de achterste (remmende) capstan zou door een riem worden aangedreven op een iets lagere snelheid om de tapespanning binnen de gesloten lus te garanderen, [ 29 ] waardoor er nauw contact tussen alle drie de koppen en de tape wordt gegarandeerd (de drukpad van de cassette kan slechts één kop bevatten), en de tape mechanisch wordt losgekoppeld van de behuizing van de cassette. [ 29 ] Een Revox-deck werkt anders en drijft elke capstan rechtstreeks aan met zijn eigen motor, uitgerust met een enorm vliegwiel en een 150-polige snelheidssensor. [ 30 ] De snelheid van elke motor wordt geregeld door een fasevergrendelde lus ; beide lussen zijn gesynchroniseerd met een gemeenschappelijke kristaloscillator . Volgens Studer werd elke capstan bewerkt met een precisie van 1 μm (0,001 mm of 0,000039 inch), om zeer lage wow en flutter te garanderen. [ 31 ] [ c ] In 1985 was het enige andere dek met een soortgelijke directe aandrijving de vijfmotorige Nakamichi Dragon (de dichtstbijzijnde concurrent, de viermotorige Tandberg 3014, gebruikte één enkele kaapstandermotor). [ 32 ] Twee andere motoren van de B215, diep in het mechanisme begraven, drijven de spoelen van de cassette rechtstreeks aan. Motoren, capstans en spoelspindels zijn gemonteerd op twee spuitgietchassisplaten, stevig aan elkaar geschroefd; koppen en aandrukrollen zijn gemonteerd op een bewegend spuitgietsubchassis. [ 31 ] [ 33 ] [ c ] Alle vier de motoren worden elektromagnetisch geremd; er zijn geen mechanische remblokken of frictiewielen. [ 33 ] [ c ] Autostop wordt geactiveerd met een opto-isolator die de aanwezigheid van transparante aanloopband detecteert . [ 27 ] Het opwinden van een band van 90 minuten duurt niet langer dan 75 seconden, [ 20 ] [ 28 ] bij een constante lineaire bandsnelheid. [ 34 ] Als de microcontroller om welke reden dan ook een abnormaal hoge bandspanning detecteert, verlaagt hij onmiddellijk de opwindsnelheid. Aan het einde van de spoel wordt de bandsnelheid geleidelijk verlaagd om impact op het einde van de band te voorkomen. [ 34 ] [ 22 ] Volgens Howard Roberson van het tijdschrift Audio (VS) was de werking van een nieuw B215-transport "...erg stil, zelfs in de afspeelmodus - misschien wel het stilste van alle tot nu toe geteste decks... zeer goed gebouwd, met een duidelijke uitstraling van betrouwbaarheid op de lange termijn". [ 21 ] De B215 gebruikt sendust- en ferrietkoppen van Canon (de B710 gebruikte Sony-koppen, de Revox reel-to-reel-koppen werden door Studer zelf vervaardigd). [ 35 ] De afspeelkop heeft een smalle magnetische opening, de opnamekop heeft een brede opening, maar de exacte breedtes van de openingen zijn niet bekendgemaakt. [ 2 ] [ 22 ] In tegenstelling tot de B710 zitten de opname- en afspeelkoppen van de B215, en een isolatiewig ertussen, strak tegen elkaar aan en kunnen niet afzonderlijk worden afgesteld. [ 22 ] Recensenten van Audio and Modern Electronics merkten een exemplarisch laag faseverschil op tussen het linker- en rechterkanaal (interchannel time error, ICTE), wat een teken was van een zeer goede uitlijning van de opname- en afspeelopeningen en een verwaarloosbaar lage relatieve azimutfout. [ 36 ] [ 37 ] ===Audiopad=== Het audiopad beslaat drie printplaten, die elk de volledige diepte van de behuizing beslaan. Van boven naar beneden: opnameprintplaat, afspeel- en besturingsprintplaat, Dolby-printplaat. Het signaalpad van de B215 is vanaf de grond af ontworpen voor gebruik met Dolby C- ruisonderdrukking. [ 12 ] De gebruikershandleiding adviseerde dat "het selecteren van ruisonderdrukking voor nieuwe platen eenvoudig is: gebruik [alleen] Dolby C". [ 38 ] Het deck maakt gebruik van vier Hitachi HA12058 Dolby B/C IC's in een "dubbele Dolby"-configuratie met onafhankelijke coderings- en decoderingskanalen. [ 39 ] Het tapetype wordt automatisch gedetecteerd, maar de gebruiker kan het tapetype handmatig overschrijven en selecteren. Dit omvat een optie om Type II (maar geen Type IV) tapes op te nemen met een equalizer van 120 μs, [ 40 ] wat wellicht de voorkeur geniet bij het opnemen van signalen met sterke hoge tonen, ten koste van meer ruis. [ d ] De B215 replay head-versterker gebruikte een discrete JFET- ingang en een bipolaire tweede trap; deze stuurt de equalizertrap aan - een actief filter gebouwd rond een operationele versterker in inverterende configuratie . [ 41 ] Subtiele fasecontrolenetwerken in het actieve filter werden afgestemd op de best mogelijke staprespons ; Ludwig schreef dat ze " blokgolfreproductie van de tape van werkelijk professionele kwaliteit" mogelijk maakten. [ 12 ] Het signaal gaat vervolgens door een CMOS- schakelaar naar de Dolby-decoder en vervolgens door een andere CMOS-schakelaar naar de uitgangsbuffertrap. [ 41 ] Een derde set CMOS-schakelaars wordt ingeschakeld om een ​​tijdconstante van 70 μs te selecteren in plaats van de standaard 120 μs; als gevolg hiervan gaat het signaal tijdens het afspelen door twee of drie CMOS-schakelaars, plus de schakelaars in de Dolby-decoder. [ 41 ] De schakelaars injecteren onvermijdelijk hun eigen vervormingsproducten in het signaal; hun prestaties kunnen worden verbeterd door vervanging van de standaard 14000-serie schakelaars voor nieuwere pin-compatibele IC's met lage impedantie. Het lijnuitgangsniveau is vast en ongebruikelijk "heet" voor consumentenaudio: 775 mV RMS voor een nominaal magnetisatieniveau van 250 nWb/m. [ 42 ] De hoofdtelefoonuitgang heeft acht selecteerbare volume-instellingen, wat voldoende is voor praktisch gebruik. [ 20 ] Het opnamepad van de audio, dat een eigen printplaat in beslag neemt, is veel complexer. Er zijn drie elektronische niveauregelaars, in serie geschakeld. Continu variabele fade-in en fade-out wordt uitgevoerd door een analoge transconductantieversterker . [ 43 ] Signaalniveaus bij de ingang van de Dolby-encoder ("opnameniveau") en bij de uitgang ("tapegevoeligheid") worden geregeld door 8-bits vermenigvuldigende DAC's . [ 43 ] Ten slotte selecteert een CMOS- multiplexer , gekoppeld aan een laag-Q banddoorlaatfilter gecentreerd op 4 kHz, de gewenste middentonen- equalisatie-instelling. [ 43 ] Nog een andere set 8-bits vermenigvuldigende DAC's, gekoppeld aan een niet-uitschakelbaar Dolby HX Pro- circuit, stelt de gewenste biasstroom in. [ 43 ] Dolby dynamische biasing verbetert, volgens Stereo Review , de verzadigingsniveaus van de hoge tonen met ongeveer 6 dB. [ 44 ] ===Microcontrollers en embedded software=== Drie Philips MAB8440 microcontrollers en EEPROM (rechts, met papieren label) De besturingsfuncties van het deck zijn verdeeld over drie identieke Philips MAB8440- microcontrollers [ 12 ] , die worden geklokt met een gemeenschappelijke6 MHz kristal . [ 45 ] Elke microcontroller draagt4 kB programmageheugen en 128 bytes RAM . [ 45 ] De eerste microcontroller controleert het frontpaneeltoetsenbord, de infraroodafstandsbedieningspoort en een optisch ontkoppelde RS-232- poort; de tweede bestuurt de motoren en berekent realtime tapetellerwaarden. De derde microcontroller beheert de digitaal-naar - analoogconverters , CMOS-switches, multiplexers en de opnameniveaumeter; hij voert het tapekalibratieprogramma uit en slaat de huidige instellingen op in niet-vluchtig geheugen . [ 12 ] Het EEPROM wordt bijgewerkt bij elke overgang naar de stand-bymodus of wanneer de gebruiker op een speciale "store"-knop drukt. [ 46 ] [ 47 ] De microcontrollers, display en DAC-drivers zijn verbonden met de I²C seriële bus, [ 45 ] die begin jaren tachtig door Philips werd geïntroduceerd; volgens Ludwig was een gestandaardiseerde bus een vereiste voor een project van een dergelijke omvang. [ 12 ] De B215 is uitgerust met een unieke realtime tapeteller. [ 48 ] Nadat de gebruiker een cassette heeft geplaatst (teruggespoeld of niet) en op de afspeelknop heeft gedrukt, schat de ingebouwde software de huidige tapepositie door de hoeksnelheden van de cassettespoelen te vergelijken. [ 48 ] De eerste schatting duurt 5–8 seconden. Het deck schat ook de volledige speelduur van een cassette, zij het met onzekerheid; om de foutmarge te verkleinen, kan de gebruiker de speelduur handmatig instellen op 46, 60, 90 of 120 minuten. [ 48 ] Met deze prompt, volgens recensenten van Audio magazine, bedraagt ​​de absolute fout niet meer dan één minuut voor een C90-cassette. [ 20 ] De transportbesturingssoftware van de B215 heeft een eigenaardige eigenaardigheid waardoor het volledig terugspoelen van de tape onmogelijk is. Nadat het deck het terugspoelen heeft voltooid, of nadat de gebruiker een reeds teruggespoelde cassette heeft geplaatst, controleert de B215 op de aanwezigheid van ondoorzichtige magneetband in het tapekanaal. Als de opto-elektronische sensor transparante aanloopband detecteert, spoelt het deck de tape langzaam vooruit totdat de sensor ondoorzichtige tape tegenkomt; deze functie kan niet handmatig worden uitgeschakeld. Het deck is dan klaar voor afspelen of opnemen, hoewel het uitvoeren van automatische kalibratie aan het begin van de magneetband ongewenst is; de gebruiker moet de tape handmatig doorspoelen naar een willekeurig punt halverwege de rol, daar kalibratie uitvoeren en handmatig terugspoelen. [ 49 ] [ 20 ] ===Tape-kalibratie=== In 1985 werd tapekalibratie, die ontbrak in de Revox B710, de facto de standaardfunctie in de industrie voor topmodellen. [ 50 ] [ 51 ] Reel-to-reel recorders hadden dit niet nodig omdat de kwart-inch tapetechnologie zich langzaam ontwikkelde, de tapes op de markt zeer vergelijkbare magnetische en elektroakoestische eigenschappen hadden, en omdat opnemen op hoge snelheid per ontwerp minder gevoelig was voor variaties in de tape-eigenschappen. [ 50 ] Cassettetapetechnologie ontwikkelde zich daarentegen snel en nieuw ontworpen premiumformules verschilden consequent van IEC-referentiebanden of de oudere, goedkopere tapes. [ 50 ] Het probleem bestond al in 1983: de B710, die in de fabriek was afgestemd op TDK SA-X ferricobalt Type II-tape , had een uitgesproken hogetonenverval bij opname op zuiver chroom IEC Type II-referentiebanden . [ 52 ] Meinrad Liebert bekritiseerde de IEC omdat deze geen strikte normen had opgelegd: de organisatie volgde simpelweg de markt en paste periodiek haar set referentietapes aan willekeurig gekozen "industriegemiddelden" aan. [ 50 ] De ongecontroleerde verspreiding van incompatibele cassettes maakte traditionele cassettedecks met vaste bias vrijwel onbruikbaar voor opnames; dit verklaarde volgens Liebert de plotselinge vraag naar kalibratiefuncties die in de jaren zeventig niet bestonden. [ 50 ] Het ontwerpteam van Revox koos voor geautomatiseerde kalibratie, hoewel de toen gangbare handmatige kalibratie niet alleen goedkoper, maar ook robuuster was. Een menselijke operator heeft een inherent voordeel bij het omgaan met onvermijdelijke drop-outs, transiënten en langzame fluctuaties in de gevoeligheid van de tape; [ 53 ] [ 51 ] volledig automatische kalibratie kon vaak niet omgaan met willekeurige onregelmatigheden en kon verschillende "optimale punten" voor dezelfde tape genereren. [ 53 ] Van de drie of vier beschikbare kalibratiestrategieën koos Liebert de meest flexibele en robuuste benadering van constante hoge tonen-equalisatie - waarbij de bias en het opnameniveau werden aangepast terwijl de equalisatie van het opnamekanaal ongewijzigd bleef, met een extra aanpassing van de frequentierespons rond de 4 kHz. [ 53 ] In tegenstelling tot de meer gebruikelijke tweetonige opstelling gebruikte de Revox dus drie testtonen [ 12 ] (de exclusieve Nakamichi 1000ZXL gebruikte er vier [ 7 ] ). Hoewel Studer er de voorkeur aan gaf deze functie alignment te noemen , heeft dit alleen invloed op de elektronica van het opnamepad en voert het geen mechanische uitlijning uit. [ 47 ] In het voorjaar van 1985 werd de kalibratiesequentie door testers van het tijdschrift Audio reverse-engineered , [ 21 ] en twee jaar later publiceerde Liebert een beschrijving van het algoritme uit de eerste hand: * Grove aanpassing van de bias (17 kHz testtoon); * Gevoeligheidsinstelling ("niveau") (400 Hz testtoon); * Fijne afstelling van bias (17 kHz testtoon); * Aanpassing van de middentonen-equalisatie (4 kHz testtoon). [ 53 ] De B215 past de bias en gevoeligheid afzonderlijk aan in elk kanaal, en de midrange-equalisatie wordt gelijktijdig in beide kanalen uitgevoerd. [ 54 ] De bias en gevoeligheid worden ingesteld met 8-bits DAC's met behulp van een binair zoekalgoritme , zodat elk van de zes aanpassingen slechts acht elementaire metingen in beslag neemt. [ 53 ] Bij 400 Hz duurt elke meting ongeveer 0,4 s: 0,1 s om de tape van de opnamekopopening naar de afspeelkop te laten lopen, en ongeveer 0,3 s om de detector tot rust te laten komen . [ 53 ] Bij 17 kHz duurt de meting nog langer, omdat de testtoon wordt opgenomen in korte bursts van 120 ms (om ongewenste overspraak van de opnamekop naar de afspeelkop te onderdrukken). [ 53 ] De volledige testsequentie duurt volgens Liebert ongeveer 25 s; [ 53 ] onafhankelijke reviewers hebben zelfs lagere tijden van ongeveer 20 s geciteerd. Dit was nog steeds veel langer dan de typische 4 tot 8 seconden die andere auto-kalibratiedecks van dezelfde generatie bereikten, [ 51 ] en bijna de 30 seconden die volgens Liebert "het geduld van de gebruiker op de proef zou stellen". [ e ] =Tests en beoordelingen= ===Onafhankelijke metingen=== Specificaties gepubliceerd door Studer waren zeer conservatief en onthulden niet het ware potentieel van het deck. [ 55 ] Directe vergelijking met Japanse concurrenten was onmogelijk, vooral wat betreft tape transport parameters. De wow en flutter rating van 0,1% van de B215 is bijvoorbeeld een maximale waarde geïnterpreteerd volgens DIN 45507 / IEC 386 , [ 56 ] terwijl de concurrenten doorgaans veel lagere root mean square (RMS) getallen gaven. Onafhankelijke tests uitgevoerd door de pers in de jaren 1980 maten van 0,01% tot 0,042% RMS, en van 0,016% tot 0,07% maximum. [ 20 ] [ 57 ] [ 26 ] [ 36 ] [ f ] Zelfs de hoogste RMS-waarde van 0,042% werd beschouwd als "opmerkelijk laag"; [ 36 ] de B215 overtrof de concurrentie of evenaarde deze met de Nakamichi Dragon. [ 44 ] [ 36 ] [ 28 ] [ 58 ] Craig Stark van Stereo Review gaf toe dat de cijfers zo dicht bij de grenzen van testinstrumenten lagen dat gemeten verschillen tussen de decks in deze klasse waarschijnlijk niet van belang waren. [ 44 ] De absolute snelheid op de lange termijn, typisch voor alle kwartsgestuurde dubbel-capstan-transporten, [ g ] was consistent 0,2–0,3% sneller dan de standaardsnelheid en vrijwel ongevoelig voor schommelingen in de netspanning. [ 20 ] [ 26 ] [ 57 ] [ 28 ] Het dynamische bereik van de B215, begrepen als het verschil tussen het A-gewogen bias-ruisniveau en het maximale uitgangsniveau bij 400 Hz, was vergelijkbaar met dat van de Tandberg 3014, maar consequent slechter dan dat van de Dragon of de Onkyo 2900. Het dynamische bereik in het slechtste geval, gemeten met kwaliteitsband van Type I zonder ruisonderdrukking en spectrale weging, was slechts gelijk aan51 dB vergeleken met de Dragon's54 dB . Beide decks hadden ongeveer dezelfde ruisvloer, bepaald door de bias-ruis (gesis) van de tape in plaats van elektronica; de Revox verloor door lagere maximale uitgangsniveaus. Volgens tests van Audio and Stereo Review bereikte de B215 met Type I- en Type IV-tapes 3% vervorming bij slechts 3–4 dB boven het Dolby-niveau, terwijl de Dragon Type IV-tapes kon opnemen en reproduceren tot wel +10 dB. Howard Roberson van Audio opperde dat de smalle overbelastingsmarge van de Revox een prijs was die betaald werd voor zijn brede frequentierespons. [ 37 ] Nederlands De B215-gebruikershandleiding specificeerde een frequentierespons van 30–18000 Hz (+2/-3 dB) voor Type I-tapes en 30–20000 Hz (+2/-3 dB) voor Type II en IV. [ 56 ] Opnieuw lieten onafhankelijke tests zien dat de prestaties de conservatieve specificaties van Studer ruimschoots overtroffen. De lage frequentierespons, gemeten door het tijdschrift Audio op -20 dB ten opzichte van het Dolby-niveau, strekt zich uit van 9–23100 Hz (± 3 dB) voor Type I- en Type IV-tapes, en tot 24500 Hz (± 3 dB) voor Type II-tape. [ 37 ] [ h ] Op Dolby-niveau, waar de frequentierespons grotendeels wordt beperkt door de tapeverzadiging in plaats van door de speler, mat de Revox 23–14100 Hz voor Type I, 23–16000 Hz voor Type II en 24–17000 Hz voor Type IV. [ 37 ] [ h ] Het gebruik van Dolby C verbreedt de schijnbare bovengrens op Dolby-niveau tot 21–23 kHz. [ 37 ] [ h ] Over het geheel genomen is de Revox-treble-extensie lager dan het record dat is gevestigd door de Nakamichi 1000ZXL (26–28 kHz [ 6 ] ), maar is typisch voor alle vlaggenschipmodellen van midden jaren tachtig. [ 55 ] Het belang van deze parameter werd vaak overdreven door hifi-enthousiastelingen en de op consumenten gerichte pers; professionals vonden het niet belangrijk omdat elk professioneel deck gemakkelijk de 20 kHz-grens overschreed. [ 55 ] De kwaliteit van de kalibratie, een vereiste voor een goede treble-respons, werd als zeer hoog beoordeeld; [ 20 ] [ 44 ] [ 28 ] De B215 wist gemakkelijk de verschillen uit te wissen tussen tapes die zo verschillend waren als BASF CR-M (multilayer chroom, aanbevolen door Studer [ 55 ] [ 44 ] ) en TDK SA (enkellaags ferricobalt). [ 44 ] De lage frequentierespons van banden die zijn opgenomen en afgespeeld op de B215 vertoont een opvallend kamvormig patroon onder de 30 Hz. [ 59 ] [ 26 ] [ 60 ] Deze "kopbobbels", die wijzen op een sterk contoureffect , verschijnen alleen tijdens het opnemen. [ 21 ] [ 61 ] De frequentierespons van de afspeelband, gemeten met testbanden, is exemplarisch vlak, [ 21 ] [ 61 ] vergelijkbaar met die van de Nakamichi Dragon, en merkbaar beter dan die van de Tandberg 3014. [ 61 ] ===Algemene evaluatie=== Recensenten tussen 1985 en 1988 gaven de B215 unaniem uitstekende beoordelingen, met name voor de kwaliteit van het bandtransport. Len Feldman van Modern Electronics schreef: "... over het algemeen ... is het werkelijk een Rolls-Royce onder de cassetterecorders. Zijn merk ontloopt prestige. Bovendien is hij gebouwd om lang mee te gaan en om na vele jaren gebruik aan alle gepubliceerde specificaties te blijven voldoen of deze zelfs te overtreffen." [ 28 ] In vergelijkende tests door Stereo Review (Verenigde Staten, 1988) en Audio (West-Duitsland, 1985) werd de B215 gerangschikt als een van de twee beste decks op de markt, de andere was de Nakamichi Dragon. [ 58 ] [ 62 ] De B215 overtrof de Dragon op mechanisch gebied, met een eenvoudiger, robuuster en duurzamer bandtransport. [ 58 ] De B215 verloor van de Dragon op het gebied van dynamisch bereik, subjectief niveau en het spectrum van ruis; andere subjectief gedetecteerde verschillen in sonische handtekeningen waren onbeduidend en konden in het voordeel van beide deelnemers worden geïnterpreteerd. [ 58 ] Op klankgebied overtroffen zowel de B215 als de Dragon de eveneens dure ASC [ b ] en Tandberg decks en de veel goedkopere vlaggenschipmodellen van Harman Kardon , Onkyo en TEAC . [ 58 ] [ 62 ] De Dragon had een voorsprong op de B215 en alle andere concurrenten vanwege het automatische azimutcorrectiesysteem. [ 63 ] De Dragon kon gemakkelijk banden "verteren" die waren opgenomen op andere, vaak verkeerd uitgelijnde, apparatuur. [ 63 ] Zijn zeskanaals, azimut-sensorische afspeelkop bleef een eenhoorn, een ongekend hoogtepunt van cassettetechnologie. Afgezien van een kortstondige poging van Marantz heeft geen enkele concurrent ooit geprobeerd deze te kopiëren. [ 64 ] De productie en aftermarket-service van azimut-sensorkoppen bleken zelfs voor Nakamichi te moeilijk, en in plaats van de Dragon-lijn te ontwikkelen, begon het bedrijf met de productie van unidirectionele automatisch omkerende decks die de cassette fysiek omdraaiden in plaats van het transport om te keren. [ 64 ] =Notities= a. Voor het dupliceren van grote volumes en goedkope cassettes werden industriële machines gebruikt die 16, 32 of zelfs 64 keer sneller draaiden dan normaal. Duplicatie op hoge snelheid was goedkoop, maar ging ten koste van de geluidskwaliteit. Een realtime duplicator gebruikte normale cassettedecks van hoge kwaliteit die op normale snelheid draaiden. Deze tapes konden zo goed klinken als de cassettetechnologie toeliet, maar realtime duplicatie was duur en alleen geschikt voor kleine oplages. b. ASC (Audio System Components) was een kleine Duitse fabrikant van hifi-apparatuur voor thuisgebruik, beter bekend om hun spoelenrecorders op basis vanBraun-transportbanden. Na de teloorgang van de hifi-industrie schakelde het bedrijf over op industriële dataregistratiediensten en is het anno 2020 nog steeds actief onder de naam ASC Technologies AG. c. Referentie beschrijft de B710 d. Overschakelen van 70 μs naar 120 μs verhoogt het A-gewogen ruisniveau met ongeveer 4 dB en verhoogt het schijnbare verzadigingsniveau van de hoge tonen met dezelfde 4 dB. Het werkelijke verzadigingsniveau, in termen van tapemagnetisatie, blijft ongewijzigd, maar het schijnbare niveau wordt versterkt door een equalizerfilter. e. Liebert schreef dat alles wat langer duurt dan 30 seconden “het geduld van de gebruiker op de proef zal stellen”. [ 53 ] f. In alle gevallen hadden de getallen betrekking op één specifieke steekproef. Deze getallen zijn slechts indicatoren van de prestaties van het deck en gelden niet voor de gehele populatie. g. Fabrikanten maakten nieuwe decks opzettelijk 0,2–0,5% sneller dan de standaard. Naarmate de decks ouder werden, zorgde slijtage van de kaapstander ervoor dat de snelheid geleidelijk terugliep naar de standaardsnelheid. Kleine snelheidsverhogingen werden als veel minder schadelijk beschouwd dan kleine snelheidsverlagingen. h. In alle gevallen gebruikte AudioMagazine de beste, duurste tapeformules - Maxell UD-XLI, TDK HX-S, TDK MA-R. [ 37 ] De Type II TDK HX-S was in feite een tape met metaaldeeltjes, ontworpen om te werken op een Type II bias. Testers selecteerden doelbewust de tapes die de beste resultaten opleverden met de B215, terwijl andere premiumformules niet zo goed presteerden. [ 37 ] bd37977f359ef971ddb6ff572def2d4306cad7aa 0 588 2847 2588 2025-07-03T07:58:54Z Pvdm 2 wikitext text/x-wiki APACHE: <pre> Apache Nginx test <VirtualHost *:80> server { listen 80; ServerName yoursite.com ServerAlias www.yoursite.com server_name yoursite.com www.yoursite.com; DocumentRoot /path/to/root root /path/to/root; AllowOverride All <span class=“highlight”>(No Available Alternative)</span> DirectoryIndex index.php index index.php; ErrorLog /path/to/log error_log /path/to/log error; CustomLog /path/to/log combined access_log /path/to/log main; Alias /url/ “/path/to/files” location /url/ { <Directory “/path/to/files”> alias /path/to/files; </pre> NGINX: <pre> server { listen 8000; # We’re deliberately leaving this as-is to avoid conflict at the moment root /var/www; server_name <span class="highlight">your_site.com</span> www.<span class="highlight">your_site.com</span>; location / { try_files $uri $uri/ /index.html; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } location /doc/ { alias /usr/share/doc/; autoindex on; allow 127.0.0.1; deny all; } location ~/\.ht { deny all; } } </pre> 99699d6a5158f0c99d4854af535ad99e2dd2427e 0 82 2848 2816 2025-07-10T11:12:58Z Pvdm 2 wikitext text/x-wiki =Convert an .MTS file to a .MP4 file= We want to convert it to .MP4, for instance to show it on a mobile device Android, or to play it om xbmc, or to import into kdenlive. ... ==For a whole directory, type:== IFS=$(echo -en "\n\b"); for i in *.MTS; do ffmpeg -i "$i" -vcodec mpeg4 -b:v 15M -acodec libmp3lame -b:a 192k "$i.mp4"; done or offtopic: <pre> find . -print0 | while read -d $'\0' file do echo -v "$file" done </pre> Now, if you want to resize it for some reason (show on mobile phone): #ffmpeg -i 00031.MTS -s 480x320 -b:v 4000k 00031.MP4 -i = input file -s = size <=== PUT THE SIZE PARAMETER JUST AFTER THE INPUTFILENAME, OTHERWISE YOU GET AN ERROR -b:v = videobitrate, 8000k gives a slightly better image, but doubles the filesize -b:a = audiobitrate Using these parameters you shrink a 25MB movie to a 6 MB movie. =Convert an .DV file to a .MP4 file= ffmpeg -i tape.dv -vcodec mpeg4 -b:v 15M -acodec libmp3lame -ab 192k -threads 2 -ilme tape.mp4 '''-ilme''' = Force interlacing support in encoder (MPEG-2 and MPEG-4 only). Use this option if your input file is interlaced and you want to keep the interlaced format for minimum losses. The alternative is to deinterlace the input stream with -deinterlace, but deinterlacing introduces losses. =Convert an .MTS file to a .DV file for video editing= We want to convert it to .DV, because then our video editing program (kdenlive) will process the clips much much faster!!! #ffmpeg -i 00005.MTS -f avi -b:v 16000k -ab 192k 00005.DV -i = input file -f = format, appeared neccessary -b:v = videobitrate, this value of 16000k is exactly the same as the source file, because we don't want any loss!! -b:a = audio bitrate, this value of 192k is exactly the same as the source file, because we don't want any loss!! ==ALTERNATIVE== I also found this commandline, worked very well: ffmpeg-kino -threads 2 -i 00120.MTS -s 720x576 -r pal -aspect 16:9 -ac 2 -ar 48000 -pix_fmt yuv420p -y 00120.MTS.dv Another commandline: ffmpeg -y -i 00141.MTS -vcodec mpeg4 -b:v 8000000 -ab 128000 -s 1280x720 new2.mp4 ffmpeg -y -i 00101.MTS -vcodec mpeg4 -b:v 14M -acodec ac3 -ab 192k new.mp4 <-- deze gebruikt om .MTS in kdenlive te importeren dus: for i in *; do ffmpeg -y -i "$i" -vcodec mpeg4 -b:v 14M -acodec ac3 -ab 192k "$i".mp4; done =Convert to WebM (VP8)= A valid WebM file can only contain VP8 video and Vorbis audio in a .webm container. ffmpeg -i bla.mp4 -vcodec libvpx -b:v 15M -acodec libvorbis -b:a 192k out.webm For web page (reduced size): # ffmpeg -i 44.mp4 -s 568x320 -vcodec libvpx -b:v 300k -acodec libvorbis -b:a 64k 44.webm =Convert an .MTS file to Flash (FLV)= ffmpeg -i bla.mts -s 640x360 -ar 22050 -b:v 1M blaat.flv of pas de bitrate aan voor hogere kwaliteit: ffmpeg -i bla.mts -s 640x360 -ar 22050 -b:v 3M blaat.flv =Convert an old analogue letterbox recording to SD digital format= The input file was <pre>Input #0, mpeg, from '1106_20091226203000.mpg': Duration: 04:24:55.20, start: 0.276144, bitrate: 6934 kb/s Stream #0.0[0x1e0]: Video: mpeg2video (Main), yuv420p, 720x576 [PAR 64:45 DAR 16:9], 8000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0.1[0x1c0]: Audio: mp2, 48000 Hz, stereo, s16, 384 kb/s </pre> and the picture has big black borders on the top and bottom and looks squashed. It was supposed to be stretched to fill up the screen (Our old analogue TV did that automatically). This must be done in 2 steps: first the cropping, then rescaling back to 16:9 The first command is ffmpeg -i input.mpg -vf crop=720:430 -vcodec mpeg2video -b:v 8M -acodec mp2 -b:a 384k 25ycrop.mpg Note that we try to keep the audio/video exactly the same as the sourcefile. The commandline options -sameq and -vcodec copy don't seem to work here. Next we must scale the video back to full screen, again the same settings for vcodec and acodec: ffmpeg -i 25ycrop.mpg -s 720x576 -aspect 16:9 -vcodec mpeg2video -b:v 8M -acodec mp2 -b:a 384k bla.mpg =Other examples= <pre> # ffmpeg -i 00039.MTS -f avi -vcodec mpeg4 -b:v 16000 bla.wmv # ffmpeg -i 00039.MTS -f avi -vcodec msmpeg4v2 -b:v 16000 bla.wmv # ffmpeg -y -i VIDEO0005.3gp -vcodec wmv2 -f avi -ar 44100 kerst2009.avi # ffmpeg -formats -> lists formats # ffmpeg -f avi -> force avi format # ffmpeg -codecs -> lists codecs # ffmpeg -vcodec mpeg4 -> use codec # ffmpeg -acodec libmp3lame -> use mp3 audio codec # ffmpeg -i <inputfile> -> show info about movie file # ffmpeg -y -> overwrite outputfiles # ffmpeg -vcodec copy -ss 00:01:00 -t 00:03:00 -i infile.mpg outfile.mpg -> this cut the file from 1 minute to 4 minutes (t=duration) or # ffmpeg -i inputfilename.mpg -sameq -ss 00:01:00 -t 00:03:00 outfile.mpg The above will extract 3 minutes of mpg file from the 1 minute mark using same quality as the source file. This is useful for Variable Bit Rate (VBR) encoded files. # ffmpeg -target dvd|vcd|svcd|dv|dv50 -> all options are set automagically, but you can overrule as long as they don't conflict w/ the standard -r --> set framerate, default = 25. also 'pal' is accepted -threads --> set thread count # ffmpeg -i 00090.MTS -f avi -b 6000k -ab 192k -vcodec mpeg2video 00090.mpg convert MTS to XBOX readable format </pre> =example command to preserve EXIF data and timestamps= $ for i in *.MOV ; do ffmpeg -i "$i" -preset slow -crf 27 "${i//.MOV}.mp4" ; exiftool -tagsFromFile "$i" "${i//.MOV}.mp4" ; touch -r "$i" "${i//.MOV}.mp4" ; done !!I should have used ${i%.MOV}.mp4 to match only the suffix pattern, not anywhere in the variable string. =example of Intel Skylake 520 vaapi encoding= # ffmpeg -threads 4 -i dcc-basf.mp4 -vaapi_device /dev/dri/renderD128 -vcodec h264_vaapi -vf format='nv12|vaapi,hwupload' output2.mp4 =Burning subtitles from embedded subtitles stream into the video image= # ffmpeg -i s01e01.mkv -c:v libx264 -c:a copy -vf "subtitles=s01e01.mkv:stream_index=1" output.mkv where stream_index is the # of the subtitle stream This gives encoding fps of around 30. '''ultrafast encoding:''' # ffmpeg -i s01e01.mkv -c:v libx264 -preset ultrafast -c:a copy -vf "subtitles=s01e01.mkv:stream_index=1" output.mkv This gives encoding fps of around 140. Note: The "'''ultrafast'''" preset will likely result in noticeable quality degradation compared to slower presets. If higher quality is important, consider using faster presets like "'''superfast'''" or "'''veryfast'''" which offer a better balance between speed and quality. For even faster encoding, you can explore hardware acceleration options like NVENC (for NVIDIA GPUs) or QuickSync (for Intel GPUs) if your system supports them. '''Intel hardware encoding: ''' # ffmpeg -i s01e01.mkv -c:v h264_qsv -c:a copy -vf "subtitles=s01e01.mkv:stream_index=1" output2.mkv This gives encoding fps of around 180 Another option: -preset veryfast =Sharpening= Using the -vf option. <pre># Strong luma sharpen effect parameters unsharp=7:7:2.5 PvdM: dit betekent [unsharp @ 0x64f7c0] effect:sharpen type:luma msize_x:7 msize_y:7 amount:2.50 # Strong blur of both luma and chroma parameters unsharp=7:7:-2:7:7:-2 # Use the default values with ffmpeg ./ffmpeg -i in.avi -vf "unsharp" out.mp4 PvdM: dit betekent [unsharp @ 0x64f7a0] effect:sharpen type:luma msize_x:5 msize_y:5 amount:1.00 </pre> Example: ffmpeg -i part1.dv -vf "unsharp" -target dvd test2.mpg PvdM: getest en werkt goed: #ffmpeg -i out.dv -vf unsharp=9:9:1.5:9:9:1.5 out2.dv =Image Stabilizing= $ ffmpeg -i $invoer -vf vidstabdetect -f null - $ ffmpeg -i $invoer -vf vidstabtransform=crop=black:smoothing=20,unsharp=5:5:0.8:3:3:0.4 $invoer.stabilized.mp4 This is a 2 trap proccess =Timestamps= To '''set''' the timestamp of the '''file''' to the video's internal '''creation date/time''', you can use: exiftool '-CreateDate>FileModifyDate' FILE  To force a date/time when converting: ffmpeg -i 00041.MTS -vcodec mpeg4 -acodec copy -timestamp 2000012312:21:34 bla.mp4 =Split video files= ffmpeg -i input.mpg -ss 00:00:10 -t 00:00:30 out1.mpg -ss is the start point in hh:mm:ss from the beginning of your video file -t is the length of time in hh:mm:ss of your new segment. -to is the end time hh:mm:ss of the new segment. So, in the above example, you're starting 10 seconds in from the beginning of the original file and ending 30 seconds later. If you want to create multiple parts in one pass then the following should work: ffmpeg -i input.mpg -ss 00:00:10 -t 00:00:30 out1.mpg -ss 00:00:35 -t 00:00:30 out2.mpg In this example, the first segment is the same as the first example, but you're also creating a second file starting at 35 seconds in and being 30 seconds long. '''Remember to use the correct encoding:''' ffmpeg -i input.mpg -ss 00:00:10 -vcodec copy -acodec copy output.mpg Cut an avi file from second 1 to 12.9. mencoder -ss 00:01 -endpos 00:12.900 -ovc copy -oac copy -o out.avi in.avi =Merge video files= To merge 2 or more files, use the 'cat' command and pipe it through ffmpeg, like this: cat 1.mpg 2.mpg | ffmpeg (-f mpeg) -i – -vcodec copy -acodec copy outfile.mpg Unfortunately, this does not work. Again, mencoder to the rescue: mencoder -oac copy -ovc copy -o output.mp4 1.mp4 2.mp4 =Flip video files= hflip and vflip ffmpeg -i input.mp4 -vf hflip,vflip,format=yuv420p -codec:v libx264 -preset medium -crf 23 -codec:a copy output.mkv The above did not work, but this did: ffmpeg -i VID_20130915_110755.mp4 -vf transpose=2,transpose=2 output.mp4 =rotate video files 90 degrees counterclockwise= ffmpeg -i 20160416_152451.mp4 -vf transpose=2 -c:a copy output.mp4 =create timelapse movie= To create a timelapse movie from images in a directory, use: mencoder "mf://*.jpg" -mf fps=5 -o test.avi -ovc lavc -lavcopts vcodec=msmpeg4v2:vbitrate=1000 I know, this is mencoder, but it works. FFmpeg uses the following format: ffmpeg -f image2 -r 10 -b:v 1M -i %03d.jpg test2.mp4 but this doesn't work. Also it requires the imagefilenames to be of name 001.jpg - 999.jpg, which is not always the case. '''Rename files sequentially''' cnt=1;for i in `ls *.jpg`; do mv ${i} ${cnt}.jpg;cnt=$((cnt+1)); done =To list available formats (supported pixel formats, video formats, and frame sizes) for a particular input device:= $ ffmpeg -f v4l2 -list_formats all -i /dev/video0 Alternatively you could use v4l2-ctl --list-formats-ext to list available formats. =To take a picture with a webcam= ffmpeg -f video4linux2 -i /dev/video0 -vframes 1 test.jpeg =To record video with a webcam= ffmpeg -f video4linux2 -s 640x480 -r 20 -i /dev/video0 -f m4v out.m4v -r = framerate =to stream live to youtube from IPCAM= ffmpeg -rtsp_transport tcp -i "rtsp://192.168.1.34:554/iphone/11?username:password" -f lavfi -i anullsrc=r=16000:cl=mono -c:a aac -ar 44100 -pix_fmt yuv420p -preset medium -s 1280x720 -bufsize 6000k -vb 6000k -maxrate 6000k -deinterlace -vcodec libx264 -crf 18 -r 50 -f flv -force_key_frames source -x264-params keyint=20:scenecut=0 "rtmp://a.rtmp.youtube.com/live2/<YT id> =record the screen, capture the desktop= Use the x11grab device: ffmpeg -video_size 1024x768 -framerate 25 -f x11grab -i :0.0+100,200 output.mp4 This will grab the image from desktop, starting with the upper-left corner at (x=100, y=200) with the width and height of 1024x768. If you need audio too you can use ALSA (see Capture/ALSA for more info): ffmpeg -video_size 1024x768 -framerate 25 -f x11grab -i :0.0+100,200 -f alsa -ac 2 -i hw:0 output.mkv Or the pulse input device: ffmpeg -video_size 1024x768 -framerate 25 -f x11grab -i :0.0+100,200 -f pulse -ac 2 -i default output.mkv Record fullscreen TV image (ziggo stream): ffmpeg -video_size 1600x900 -framerate 30 -f x11grab -i :0.0 -c:v libx264 -qp 0 -preset ultrafast -f pulse -ac 2 -i default capture.mkv deze werkt: ffmpeg -video_size 1920x1080 -framerate 15 -f x11grab -i :0.0 -f pulse -ac 2 -i default -c:v libx264 -qp 0 -preset ultrafast capture.mkv =Merging video and audio, with audio re-encoding= See this example, taken from this blog entry but updated for newer syntax. It should be something to the effect of: ffmpeg -i video.mp4 -i audio.wav -c:v copy -c:a aac -strict experimental output.mp4 Here, we assume that the video file does not contain any audio stream yet, and that you want to have the same output format (here, MP4) as the input format. The above command transcodes the audio, since MP4s cannot carry PCM audio streams. You can use any other desired audio codec if you want. See the AAC Encoding Guide for more info. If your audio or video stream is longer, you can add the -shortest option so that ffmpeg will stop encoding once one file ends. ==Copying the audio without re-encoding== If your output container can handle (almost) any codec – like MKV – then you can simply copy both audio and video streams: ffmpeg -i video.mp4 -i audio.wav -c copy output.mkv ==Replacing audio stream== If your input video already contains audio, and you want to replace it, you need to tell ffmpeg which audio stream to take: ffmpeg -i video.mp4 -i audio.wav -c:v copy -c:a aac -strict experimental -map 0:v:0 -map 1:a:0 output.mp4 The map option makes ffmpeg only use the first video stream from the first input and the first audio stream from the second input for the output file. =extract images from a video= ffmpeg -i giveafuck.mp4 image-%3d.jpeg -r This is used to set the frame rate of video. i.e. no. of frames to be extracted into images per second. The default value is 25, using which, would have yielded a large number of images. ==Create a thumbnail image every X seconds of the video== Output a single frame from the video into an image file: ffmpeg -i input.flv -ss 00:00:14.435 -vframes 1 out.png This example will seek to the position of 0h:0m:14sec:435msec and output one frame (-vframes 1) from that position into a PNG file. Output one image every second, named out1.png, out2.png, out3.png, etc.: ffmpeg -i input.flv -vf fps=1 out%d.png Output one image every minute, named img001.jpg, img002.jpg, img003.jpg, etc. The %03d dictates that the ordinal number of each output image will be formatted using 3 digits: ffmpeg -i myvideo.avi -vf fps=1/60 img%03d.jpg Output one image every ten minutes: ffmpeg -i test.flv -vf fps=1/600 thumb%04d.bmp ==Merge pictures into an Animated GIF== convert -delay <ticks>x<ticks-per-second> -loop 0 out*gif <output-gif-file> In the command, "-delay" is an option that controls the animation speed. This option indicates that [ticks/ticks-per-second] seconds must elapse before the display of the next frame. The "-loop 0" option indicates infinite loops of animation. If you want, you can specify "-loop N", in which case the animation will repeat itself N times. For example, to create an animated GIF image with 20 frames-per-second and infinite loop, use the following command. $ convert -delay 1x20 -loop 0 out*.gif animation.gif '''The last (optional) step is to reduce the size of the created GIF file''', by using ImageMagick's GIF optimizer. Use the following command to reduce the GIF size. $ convert -layers Optimize animation.gif animation_small.gif =DVD= ==Rip entire DVD== # cat *.VOB | ffmpeg -i - -acodec aac -aq 100 -ac 2 -vcodec libx264 -crf 24 -threads 0 /data/pil.mp4 ==Re-encode for DVD use== # mythreplex --demux --fix_sync -o /data/stream -v 224 -c 128 "/data/newfile2.mpg # tcrequant /data/stream.mv2 /data/video.small.m2v 1.17052143685 ==Pull Chapters from VOB== You can pull chapters from VOB files using mplayer. Here's a command line to pull chapter 3 from the DVD drive and dump it to a VOB. mplayer dvd:// -chapter 3-3 -dumpstream -dumpfile 3.vob * physical DVD mplayer dvd://2 -chapter 3-3 -dumpstream -dumpfile ~/3.VOB * DVD .iso image mplayer dvd://2 -dvd-device "$dvd_iso" -chapter 3-3 -dumpstream -dumpfile ~/3.VOB ==Rip VOB to mpeg4== and '''deinterlace''' as well. ffmpeg -i VTS_01_1.VOB -vcodec mpeg4 -b:v 10M -acodec copy -deinterlace lan1deinterlaced.mp4 ==Rip VOB to DV== The following command will rip a VOB file strait from an unencrypted DVD and convert it to a strait DV file. ffmpeg -i /cdrom/VIDEO_TS/VTS_01_1.VOB -target dv /home/joel/Videos/game_vi.dv ==Rip VOB to DVD== The following command will rip a VOB file to an MPEG2 video with AC3 audio for a DVD. It also uses the '-sameq' option which uses the same quality factor in the encoder as in the decoder, allowing almost lossless encoding. ffmpeg -i myfile.vob -target dvd -sameq myfile.mpg ==Rip VOB to VCD== The following command will rip a VOB file to a MPEG1 video with MP1 audio. ffmpeg -i myfile.vob -target vcd myfile.mpg ==Rip VOB to Flash (FLV)== The following command will rip a VOB file to 352×240 (the same size as VCD) and will save it as a flash file. ffmpeg -i myfile.vob -s 352x240 myfile.flv ==Rip VOB to FLAC audio== The following command will extract an AUDIO-DVD files to flac. List the VOB files in order: cat VTS_01_1.VOB VTS_01_2.VOB | ffmpeg -i - -acodec flac -vn output.flac unfortunately, there will be no CUE file. =Audio= ==Adjust volume of audio file== ffmpeg -i input.wav -af "volume=5dB" output.mp3 gives a 5 dB gain ==combine multiple sources to one destination== # ffmpeg -f concat -i /tmp/list.txt output3.flac where list.txt contains: file '/tmp/file1' file '/tmp/file2' or try: ffmpeg -i "concat:input1.mpg|input2.mpg|input3.mpg" -c copy output.mpg better still: ffmpeg -f concat -i <( for f in *.wav; do echo "file '$(pwd)/$f'"; done ) output.wav ==Convert .dsf files (SACD) to standard .wav files (PCM - CD quality)== ffmpeg -i 04.dsf -acodec pcm_s16le -ar 44100 -ac 2 output.wav This however, does not give enough audio quality. '''The Golden Line:''' ffmpeg -i input.dsf -acodec pcm_s24le -ar 44100 -ac 2 44100_24.wav I have tried it with 32 bits and with 88200 and higher, could not hear it. ==copy/convert from multistream sources== Given the following input file: <pre> # fmpeg -i input.mkv ffmpeg version ... Copyright (c) 2000-2012 the FFmpeg developers ... Input #0, matroska,webm, from 'input.mkv': Duration: 01:39:44.02, start: 0.000000, bitrate: 5793 kb/s Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default) Stream #0:1(ger): Audio: dts (DTS), 48000 Hz, 5.1(side), s16, 1536 kb/s (default) Stream #0:2(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), s16, 1536 kb/s Stream #0:3(ger): Subtitle: text (default)</pre> If we want to extract only audio streams, from input file, then we can do it like this: ffmpeg -i input.mkv -map 0:1 -map 0:2 -c copy output.mkv or use the appropriate codecs ==Create multichannel WAVs or FLACs== This command will 'rip' the first 5 minutes (which is the first song actually) of a quadraphonic (4.0) .WAV file that is 45 minutes long: ffmpeg -i The\ Doobie\ Bothers-\ Toulouse\ Street.wav -acodec pcm_s16le -b:a 1400k -ss 0:0:0 -t 0:5:0 \ -ac 4 -map_channel 0.0.0 -map_channel 0.0.1 -map_channel 0.0.4 -map_channel 0.0.5 output.wav -y The resulting file 'output.wav' will be a multichannel wav with the following channel order: 1. front left 2. front right 3. rear left 4. rear right When loaded into audacity, and then when exported into either .WAV or .FLAC move the channel slider to 6 channels and the following channel mix must be done: output 1 -> channel: 1 output 2 -> channel: 2 output 3 -> channel: 5 output 4 -> channel: 6 === Extract channels from multitrack sources === To extract the center channel (channel 3, counting the channels starts at 0) which is usually the solo voice and/or other interesting discrete stuff: # ffmpeg -i yes.flac -ac 1 -map_channel 0.0.2 center.flac === Channel identification === I found this: <pre>The track order of all 5.1 surround files follows the standard as defined by SMPT/EBU and implemented by SourceForge in FLAC (v. 1.2.1b): L – R – C – Lfe – Ls - Rs flac.sourceforge.net </pre> Also: In accordance with ANSI/CEA-863-A<ref>[http://www.ce.org/PDF/Audio_Setup_Connections.pdf Consumer Electronics Association standards: Setup and Connection]</ref> {|class="wikitable sortable" |- ! [[Zero-based]] order within multi-channel<br>[[MP3 Surround|mp3]]/[[wav]]/[[flac]] datastream ! Order within <br>[[DTS (sound system)|DTS]]/[[Advanced Audio Coding|AAC]] ! Channel name ! Color-coding on commercial receiver and cabling |- |0 |1 |Front left |style="background:white"|White |- |1 |2 |Front right |style="background:red"|Red |- |2 |0 |Center |style="background:limegreen"|Green |- |3 |5 |Low frequency |style="background:SlateBlue"|Purple |- |4 |3 |Surround left |style="background:dodgerblue"|Blue |- |5 |4 |Surround right |style="background:gray"|Grey |- |6 |6 |Surround back left |style="background:saddlebrown"|Brown |- |7 |7 |Surround back right |style="background:khaki"|Khaki |} {|class="wikitable" |- |style="background:white"|Front left |style="background:limegreen"|Center |style="background:red;text-align:right"|Front right |- |style="background:dodgerblue"|Surround left | |style="background:gray;text-align:right"|Surround right |- |style="background:saddlebrown"|Surround back left | |style="background:khaki;text-align:right"|Surround back right |- |style="background:SlateBlue;text-align:center" colspan="3"|Low frequency |} === Standard speaker channels === This table shows the various speaker configurations that are commonly used for end-user equipment. The order and identifiers are those specified for the channel mask in the standard uncompressed [[WAV]] file format (which contains a raw multichannel [[Pulse-code modulation|PCM]] stream) and are used according to the same specification for most PC connectible digital sound hardware and PC operating systems capable of handling multiple channels. While it is certainly possible to build any speaker configuration, there isn't a lot of commercially available movie or music content for alternative speaker configurations. Such cases, however, can be worked around by remixing the source content channels to the speaker channels using a matrix table specifying how much of each content channel is played through each speaker channel. === Standard speaker channels === This table shows the various speaker configurations that are commonly used for end-user equipment. The order and identifiers are those specified for the channel mask in the standard uncompressed [[WAV]] file format (which contains a raw multichannel [[Pulse-code modulation|PCM]] stream) and are used according to the same specification for most PC connectible digital sound hardware and PC operating systems capable of handling multiple channels.<ref>[http://msdn.microsoft.com/en-us/library/ms791058.aspx The configuration of channels within the data format of an audio stream]</ref><ref>[http://www.khronos.org/registry/sles/api/1.0.1/OpenSLES.h Header file for OpenSL, containing various identifier definitions]</ref> While it is certainly possible to build any speaker configuration, there isn't a lot of commercially available movie or music content for alternative speaker configurations. Such cases, however, can be worked around by remixing the source content channels to the speaker channels using a matrix table specifying how much of each content channel is played through each speaker channel. ==Downmix of multichannel 5.1 audio to real quad 4 channel four speaker== A lot of surround music today is supplied in a 5.1 channel format. That means front left, front right, center, subwoofer, rear left, and rear right channel. But if you have a quadraphonic setup like me, you only have 4 speakers, which are real speakers, so no subwoofer is present nor needed. And the center speaker is also absent. So you have left front, right front, left rear and right rear. But then you have a problem with the voices in the surround mix, which are usually mixed on the center channel. Sometimes the vocals are ONLY mixed into the center channel. Without a center channel setup, you will hear no vocals. Sometimes vocals are duplicated in the front left and right channel in the audio mix, but then the vocals will sound thin, if present at all. So what is needed is a downmix of the center channel to the two front channels. Or in other words: <pre> quad destination: 5.1 source: left front <- left front + center channel right front <- right front + center channel left rear <- left rear right rear <- right rear </pre> This can be achieved by the following ffmpeg command: (where $i is the surround file) ffmpeg -i "$i" -af "pan=quad|c0<c0+c2|c1<c1+c2|c2=c4|c3=c5" "$i.flac" Or, for a complete directory: IFS=$(echo -en "\n\b"); for i in *.wav; do ffmpeg -i "$i" -af "pan=quad|c0<c0+c2|c1<c1+c2|c2=c4|c3=c5" "$i.flac"; done ==Compand== ffmpeg -i input.wav -filter:a "dynaudnorm" output.wav You will most likely need to tweak the filter options for your particular use case. Use the examples given for the compand filter as a starting point: Make music with both quiet and loud passages suitable for listening to in a noisy environment: compand=.3|.3:1|1:-90/-60|-60/-40|-40/-30|-20/-20:6:0:-90:0.2 Another example for audio with whisper and explosion parts: compand=0|0:1|1:-90/-900|-70/-70|-30/-9|0/-3:6:0:0:0 Here, the second example's options are, specifically: <pre>attacks=0|0 decays=1|1 points=-90/-900|-70/-70|-30/-9|0/-3 soft-knee=6 gain=0 volume=0 delay=0</pre> You may adjust the gain to keep the same dynamic processing but adjust it to your baseline input level. More examples: Make music with both quiet and loud passages suitable for listening to in a noisy environment: compand=.3|.3:1|1:-90/-60|-60/-40|-40/-30|-20/-20:6:0:-90:0.2 Another example for audio with whisper and explosion parts: compand=0|0:1|1:-90/-900|-70/-70|-30/-9|0/-3:6:0:0:0 A noise gate for when the noise is at a lower level than the signal: compand=.1|.1:.2|.2:-900/-900|-50.1/-900|-50/-50:.01:0:-90:.1 Here is another noise gate, this time for when the noise is at a higher level than the signal (making it, in some ways, similar to squelch): compand=.1|.1:.1|.1:-45.1/-45.1|-45/-900|0/-900:.01:45:-90:.1 2:1 compression starting at -6dB: compand=points=-80/-80|-6/-6|0/-3.8|20/3.5 2:1 compression starting at -9dB: compand=points=-80/-80|-9/-9|0/-5.3|20/2.9 2:1 compression starting at -12dB: compand=points=-80/-80|-12/-12|0/-6.8|20/1.9 2:1 compression starting at -18dB: compand=points=-80/-80|-18/-18|0/-9.8|20/0.7 3:1 compression starting at -15dB: compand=points=-80/-80|-15/-15|0/-10.8|20/-5.2 Compressor/Gate: compand=points=-80/-105|-62/-80|-15.4/-15.4|0/-12|20/-7.6 Expander: compand=attacks=0:points=-80/-169|-54/-80|-49.5/-64.6|-41.1/-41.1|-25.8/-15|-10.8/-4.5|0/0|20/8.3 Hard limiter at -6dB: compand=attacks=0:points=-80/-80|-6/-6|20/-6 Hard limiter at -12dB: compand=attacks=0:points=-80/-80|-12/-12|20/-12 Hard noise gate at -35 dB: compand=attacks=0:points=-80/-115|-35.1/-80|-35/-35|20/20 Soft limiter: compand=attacks=0:points=-80/-80|-12.4/-12.4|-6/-8|0/-6.8|20/-2.8 =HTC Hero= For the HTC Hero (Android) the default movie properties are: <pre> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '26112009004.mp4': Duration: 00:00:39.06, start: 0.000000, bitrate: 424 kb/s Stream #0.0(und): Video: mpeg4, yuv420p, 320x240 [PAR 1:1 DAR 4:3], 372 kb/s, 15 tbr, 30k tbn, 30k tbc Stream #0.1(und): Audio: aac, 48000 Hz, mono, s16, 48 kb/s Metadata major_brand : mp42 minor_version : 0 compatible_brands: mp423gp4isom </pre> =HTC Desire= Screen size: 800x480 For the Desire, the default movie properties are: *Convert .MTS files for Desire: for i in * ; do ffmpeg -i $i -s 800x480 -b 8000k /media/disk/DCIM/oostenrijk\ videos/$i.MP4; done =Samsung Galaxy S Plus= Screen size: 800x480 ==Encode videos for Samsung Galaxy S Plus== ffmpeg -i "27.mp4" -s 800x480 -vcodec mpeg4 -b 768k -acodec libmp3lame -ab 128k -dmix_mode loro "27.mobile.mp4" where * 512k gives rather bad image * 1M gives perfect image * 768k hits the sweetspot *-dmix_mode loro is used for downmixing surround sound =Codecs= =='''most used''' video codecs that ffmpeg can encode== <b>WARNING!!! DEPRECATED !!!!!!!</b> <pre> Codecs: D..... = Decoding supported .E.... = Encoding supported ..V... = Video codec ..A... = Audio codec ..S... = Subtitle codec ...S.. = Supports draw_horiz_band ....D. = Supports direct rendering method 1 .....T = Supports weird frame truncation ------ dvvideo DV (Digital Video) flashsv Flash Screen Video flc Flash Video (FLV) / Sorenson Spark / Sorenson H.263 libtheora libtheora Theora libx264 libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 libxvid libxvidcore MPEG-4 part 2 mjpeg MJPEG (Motion JPEG) mpeg1video MPEG-1 video mpeg2video MPEG-2 video mpeg4 MPEG-4 part 2 msmpeg4 MPEG-4 part 2 Microsoft variant version 3 msmpeg4v1 MPEG-4 part 2 Microsoft variant version 1 msmpeg4v2 MPEG-4 part 2 Microsoft variant version 2 wmv1 Windows Media Video 7 wmv2 Windows Media Video 8 </pre> =='''all''' video codecs that ffmpeg can encode== <pre> Codecs: D..... = Decoding supported .E.... = Encoding supported ..V... = Video codec ..A... = Audio codec ..S... = Subtitle codec ...I.. = Intra frame-only codec ....L. = Lossy compression .....S = Lossless compression ------- D.VI.. 012v Uncompressed 4:2:2 10-bit D.V.L. 4xm 4X Movie D.VI.S 8bps QuickTime 8BPS video .EVIL. a64_multi Multicolor charset for Commodore 64 (encoders: a64multi ) .EVIL. a64_multi5 Multicolor charset for Commodore 64, extended with 5th color (colram) (encoders: a64multi5 ) D.V..S aasc Autodesk RLE D.VIL. aic Apple Intermediate Codec DEVIL. amv AMV Video D.V.L. anm Deluxe Paint Animation D.V.L. ansi ASCII/ANSI art DEVIL. asv1 ASUS V1 DEVIL. asv2 ASUS V2 D.VIL. aura Auravision AURA D.VIL. aura2 Auravision Aura 2 D.V... avrn Avid AVI Codec DEVI.. avrp Avid 1:1 10-bit RGB Packer D.V.L. avs AVS (Audio Video Standard) video DEVI.. avui Avid Meridien Uncompressed DEVI.. ayuv Uncompressed packed MS 4:4:4:4 D.V.L. bethsoftvid Bethesda VID video D.V.L. bfi Brute Force & Ignorance D.V.L. binkvideo Bink video D.VI.. bintext Binary text DEVI.S bmp BMP (Windows and OS/2 bitmap) D.V..S bmv_video Discworld II BMV video D.VI.S brender_pix BRender PIX image D.V.L. c93 Interplay C93 D.V.L. cavs Chinese AVS (Audio Video Standard) (AVS1-P2, JiZhun profile) D.V.L. cdgraphics CD Graphics video D.VIL. cdxl Commodore CDXL video D.V.L. cinepak Cinepak DEVIL. cljr Cirrus Logic AccuPak D.VI.S cllc Canopus Lossless Codec D.V.L. cmv Electronic Arts CMV video (decoders: eacmv ) D.V... cpia CPiA video format D.V..S cscd CamStudio (decoders: camstudio ) D.VIL. cyuv Creative YUV (CYUV) D.V.L. dfa Chronomaster DFA DEV.LS dirac Dirac (decoders: dirac libschroedinger ) (encoders: libschroedinger ) DEVIL. dnxhd VC3/DNxHD DEVI.S dpx DPX image D.V.L. dsicinvideo Delphine Software International CIN video DEVIL. dvvideo DV (Digital Video) D.V..S dxa Feeble Files/ScummVM DXA D.VI.S dxtory Dxtory D.V.L. escape124 Escape 124 D.V.L. escape130 Escape 130 D.VILS exr OpenEXR image DEV..S ffv1 FFmpeg video codec #1 DEVI.S ffvhuff Huffyuv FFmpeg variant DEV..S flashsv Flash Screen Video v1 DEV.L. flashsv2 Flash Screen Video v2 D.V..S flic Autodesk Animator Flic video DEV.L. flv1 FLV / Sorenson Spark / Sorenson H.263 (Flash Video) (decoders: flv ) (encoders: flv ) D.V..S fraps Fraps D.VI.S frwu Forward Uncompressed D.V.L. g2m Go2Meeting DEV..S gif GIF (Graphics Interchange Format) DEV.L. h261 H.261 DEV.L. h263 H.263 / H.263-1996, H.263+ / H.263-1998 / H.263 version 2 D.V.L. h263i Intel H.263 DEV.L. h263p H.263+ / H.263-1998 / H.263 version 2 DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_vdpau ) (encoders: libx264 libx264rgb ) DEVI.S huffyuv HuffYUV D.V.L. idcin id Quake II CIN video (decoders: idcinvideo ) D.VI.. idf iCEDraw text D.V.L. iff_byterun1 IFF ByteRun1 (decoders: iff ) D.V.L. iff_ilbm IFF ILBM (decoders: iff ) D.V.L. indeo2 Intel Indeo 2 D.V.L. indeo3 Intel Indeo 3 D.V.L. indeo4 Intel Indeo Video Interactive 4 D.V.L. indeo5 Intel Indeo Video Interactive 5 D.V.L. interplayvideo Interplay MVE video DEVILS jpeg2000 JPEG 2000 DEVILS jpegls JPEG-LS D.VIL. jv Bitmap Brothers JV video D.V.L. kgv1 Kega Game Video D.V.L. kmvc Karl Morton's video codec D.VI.S lagarith Lagarith lossless .EVI.S ljpeg Lossless JPEG D.VI.S loco LOCO D.V.L. mad Electronic Arts Madcow Video (decoders: eamad ) D.VIL. mdec Sony PlayStation MDEC (Motion DECoder) D.V.L. mimic Mimic DEVIL. mjpeg Motion JPEG D.VIL. mjpegb Apple MJPEG-B D.V.L. mmvideo American Laser Games MM Video D.V.L. motionpixels Motion Pixels video DEV.L. mpeg1video MPEG-1 video (decoders: mpeg1video mpeg1video_vdpau ) DEV.L. mpeg2video MPEG-2 video (decoders: mpeg2video mpegvideo mpegvideo_vdpau ) DEV.L. mpeg4 MPEG-4 part 2 (decoders: mpeg4 mpeg4_vdpau ) (encoders: mpeg4 libxvid ) D.V.L. mpegvideo_xvmc MPEG-1/2 video XvMC (X-Video Motion Compensation) D.V.L. msa1 MS ATC Screen D.V.L. msmpeg4v1 MPEG-4 part 2 Microsoft variant version 1 DEV.L. msmpeg4v2 MPEG-4 part 2 Microsoft variant version 2 DEV.L. msmpeg4v3 MPEG-4 part 2 Microsoft variant version 3 (decoders: msmpeg4 ) (encoders: msmpeg4 ) D.V..S msrle Microsoft RLE D.V.L. mss1 MS Screen 1 D.VIL. mss2 MS Windows Media Video V9 Screen DEV.L. msvideo1 Microsoft Video 1 D.VI.S mszh LCL (LossLess Codec Library) MSZH D.V.L. mts2 MS Expression Encoder Screen D.VIL. mvc1 Silicon Graphics Motion Video Compressor 1 D.VIL. mvc2 Silicon Graphics Motion Video Compressor 2 D.V.L. mxpeg Mobotix MxPEG video D.V.L. nuv NuppelVideo/RTJPEG D.V.L. paf_video Amazing Studio Packed Animation File Video DEVI.S pam PAM (Portable AnyMap) image DEVI.S pbm PBM (Portable BitMap) image DEVI.S pcx PC Paintbrush PCX image DEVI.S pgm PGM (Portable GrayMap) image DEVI.S pgmyuv PGMYUV (Portable GrayMap YUV) image D.VIL. pictor Pictor/PC Paint DEV..S png PNG (Portable Network Graphics) image DEVI.S ppm PPM (Portable PixelMap) image DEVIL. prores Apple ProRes (iCodec Pro) (decoders: prores prores_lgpl ) (encoders: prores prores_aw prores_ks ) D.VIL. ptx V.Flash PTX image D.VI.S qdraw Apple QuickDraw D.V.L. qpeg Q-team QPEG DEV..S qtrle QuickTime Animation (RLE) video DEVI.S r10k AJA Kona 10-bit RGB Codec DEVI.S r210 Uncompressed RGB 10-bit DEVI.S rawvideo raw video D.VIL. rl2 RL2 video DEV.L. roq id RoQ video (decoders: roqvideo ) (encoders: roqvideo ) D.V.L. rpza QuickTime video (RPZA) DEV.L. rv10 RealVideo 1.0 DEV.L. rv20 RealVideo 2.0 D.V.L. rv30 RealVideo 3.0 D.V.L. rv40 RealVideo 4.0 D.V.L. sanm LucasArts SMUSH video DEVI.S sgi SGI image D.VI.S sgirle SGI RLE 8-bit D.V.L. smackvideo Smacker video (decoders: smackvid ) D.V.L. smc QuickTime Graphics (SMC) D.V... smv Sigmatel Motion Video (decoders: smvjpeg ) DEV.LS snow Snow D.VIL. sp5x Sunplus JPEG (SP5X) DEVI.S sunrast Sun Rasterfile image DEV.L. svq1 Sorenson Vector Quantizer 1 / Sorenson Video 1 / SVQ1 D.V.L. svq3 Sorenson Vector Quantizer 3 / Sorenson Video 3 / SVQ3 DEVI.S targa Truevision Targa image D.VI.. targa_y216 Pinnacle TARGA CineWave YUV16 D.V.L. tgq Electronic Arts TGQ video (decoders: eatgq ) D.V.L. tgv Electronic Arts TGV video (decoders: eatgv ) DEV.L. theora Theora (encoders: libtheora ) D.VIL. thp Nintendo Gamecube THP video D.V.L. tiertexseqvideo Tiertex Limited SEQ video DEVI.S tiff TIFF image D.VIL. tmv 8088flex TMV D.V.L. tqi Electronic Arts TQI video (decoders: eatqi ) D.V.L. truemotion1 Duck TrueMotion 1.0 D.V.L. truemotion2 Duck TrueMotion 2.0 D.V..S tscc TechSmith Screen Capture Codec (decoders: camtasia ) D.V.L. tscc2 TechSmith Screen Codec 2 D.VIL. txd Renderware TXD (TeXture Dictionary) image D.V.L. ulti IBM UltiMotion (decoders: ultimotion ) DEVI.S utvideo Ut Video DEVI.S v210 Uncompressed 4:2:2 10-bit D.VI.S v210x DEVI.. v308 Uncompressed packed 4:4:4 DEVI.. v408 Uncompressed packed QT 4:4:4:4 DEVI.S v410 Uncompressed 4:4:4 10-bit D.V.L. vb Beam Software VB D.VI.S vble VBLE Lossless Codec D.V.L. vc1 SMPTE VC-1 (decoders: vc1 vc1_vdpau ) D.V.L. vc1image Windows Media Video 9 Image v2 D.VIL. vcr1 ATI VCR1 D.VIL. vixl Miro VideoXL (decoders: xl ) D.V.L. vmdvideo Sierra VMD video D.V..S vmnc VMware Screen Codec / VMware Video D.V.L. vp3 On2 VP3 D.V.L. vp5 On2 VP5 D.V.L. vp6 On2 VP6 D.V.L. vp6a On2 VP6 (Flash version, with alpha channel) D.V.L. vp6f On2 VP6 (Flash version) DEV.L. vp8 On2 VP8 (decoders: vp8 libvpx ) (encoders: libvpx ) ..V.L. vp9 Google VP9 D.V.L. webp WebP DEV.L. wmv1 Windows Media Video 7 DEV.L. wmv2 Windows Media Video 8 D.V.L. wmv3 Windows Media Video 9 (decoders: wmv3 wmv3_vdpau ) D.V.L. wmv3image Windows Media Video 9 Image D.VIL. wnv1 Winnov WNV1 D.V.L. ws_vqa Westwood Studios VQA (Vector Quantized Animation) video (decoders: vqavideo ) D.V.L. xan_wc3 Wing Commander III / Xan D.V.L. xan_wc4 Wing Commander IV / Xxan D.VI.. xbin eXtended BINary text DEVI.S xbm XBM (X BitMap) image DEVIL. xface X-face image DEVI.S xwd XWD (X Window Dump) image DEVI.. y41p Uncompressed YUV 4:1:1 12-bit D.V.L. yop Psygnosis YOP Video DEVI.. yuv4 Uncompressed packed 4:2:0 D.V..S zerocodec ZeroCodec Lossless Video DEVI.S zlib LCL (LossLess Codec Library) ZLIB DEV..S zmbv Zip Motion Blocks Video D.A.L. 8svx_exp 8SVX exponential D.A.L. 8svx_fib 8SVX fibonacci DEA.L. aac AAC (Advanced Audio Coding) (encoders: aac libvo_aacenc ) D.A.L. aac_latm AAC LATM (Advanced Audio Coding LATM syntax) DEA.L. ac3 ATSC A/52A (AC-3) (encoders: ac3 ac3_fixed ) D.A.L. adpcm_4xm ADPCM 4X Movie DEA.L. adpcm_adx SEGA CRI ADX ADPCM D.A.L. adpcm_afc ADPCM Nintendo Gamecube AFC D.A.L. adpcm_ct ADPCM Creative Technology D.A.L. adpcm_dtk ADPCM Nintendo Gamecube DTK D.A.L. adpcm_ea ADPCM Electronic Arts D.A.L. adpcm_ea_maxis_xa ADPCM Electronic Arts Maxis CDROM XA D.A.L. adpcm_ea_r1 ADPCM Electronic Arts R1 D.A.L. adpcm_ea_r2 ADPCM Electronic Arts R2 D.A.L. adpcm_ea_r3 ADPCM Electronic Arts R3 D.A.L. adpcm_ea_xas ADPCM Electronic Arts XAS DEA.L. adpcm_g722 G.722 ADPCM (decoders: g722 ) (encoders: g722 ) DEA.L. adpcm_g726 G.726 ADPCM (decoders: g726 ) (encoders: g726 ) D.A.L. adpcm_ima_amv ADPCM IMA AMV D.A.L. adpcm_ima_apc ADPCM IMA CRYO APC D.A.L. adpcm_ima_dk3 ADPCM IMA Duck DK3 D.A.L. adpcm_ima_dk4 ADPCM IMA Duck DK4 D.A.L. adpcm_ima_ea_eacs ADPCM IMA Electronic Arts EACS D.A.L. adpcm_ima_ea_sead ADPCM IMA Electronic Arts SEAD D.A.L. adpcm_ima_iss ADPCM IMA Funcom ISS D.A.L. adpcm_ima_oki ADPCM IMA Dialogic OKI DEA.L. adpcm_ima_qt ADPCM IMA QuickTime D.A.L. adpcm_ima_rad ADPCM IMA Radical D.A.L. adpcm_ima_smjpeg ADPCM IMA Loki SDL MJPEG DEA.L. adpcm_ima_wav ADPCM IMA WAV D.A.L. adpcm_ima_ws ADPCM IMA Westwood DEA.L. adpcm_ms ADPCM Microsoft D.A.L. adpcm_sbpro_2 ADPCM Sound Blaster Pro 2-bit D.A.L. adpcm_sbpro_3 ADPCM Sound Blaster Pro 2.6-bit D.A.L. adpcm_sbpro_4 ADPCM Sound Blaster Pro 4-bit DEA.L. adpcm_swf ADPCM Shockwave Flash D.A.L. adpcm_thp ADPCM Nintendo Gamecube THP D.A.L. adpcm_xa ADPCM CDROM XA DEA.L. adpcm_yamaha ADPCM Yamaha DEA..S alac ALAC (Apple Lossless Audio Codec) DEA.L. amr_nb AMR-NB (Adaptive Multi-Rate NarrowBand) (decoders: amrnb libopencore_amrnb ) (encoders: libopencore_amrnb ) D.A.L. amr_wb AMR-WB (Adaptive Multi-Rate WideBand) (decoders: amrwb libopencore_amrwb ) D.A..S ape Monkey's Audio D.A.L. atrac1 Atrac 1 (Adaptive TRansform Acoustic Coding) D.A.L. atrac3 Atrac 3 (Adaptive TRansform Acoustic Coding 3) ..A.L. atrac3p Sony ATRAC3+ D.A.L. binkaudio_dct Bink Audio (DCT) D.A.L. binkaudio_rdft Bink Audio (RDFT) D.A.L. bmv_audio Discworld II BMV audio ..A.L. celt Constrained Energy Lapped Transform (CELT) DEA.L. comfortnoise RFC 3389 Comfort Noise D.A.L. cook Cook / Cooker / Gecko (RealAudio G2) D.A.L. dsicinaudio Delphine Software International CIN audio DEA.LS dts DCA (DTS Coherent Acoustics) (decoders: dca ) (encoders: dca ) ..A.L. dvaudio DEA.L. eac3 ATSC A/52B (AC-3, E-AC-3) D.A.L. evrc EVRC (Enhanced Variable Rate Codec) DEA..S flac FLAC (Free Lossless Audio Codec) DEA.L. g723_1 G.723.1 D.A.L. g729 G.729 DEA.L. gsm GSM (decoders: gsm libgsm ) (encoders: libgsm ) DEA.L. gsm_ms GSM Microsoft variant (decoders: gsm_ms libgsm_ms ) (encoders: libgsm_ms ) D.A.L. iac IAC (Indeo Audio Coder) ..A.L. ilbc iLBC (Internet Low Bitrate Codec) D.A.L. imc IMC (Intel Music Coder) D.A.L. interplay_dpcm DPCM Interplay D.A.L. mace3 MACE (Macintosh Audio Compression/Expansion) 3:1 D.A.L. mace6 MACE (Macintosh Audio Compression/Expansion) 6:1 D.A..S mlp MLP (Meridian Lossless Packing) D.A.L. mp1 MP1 (MPEG audio layer 1) (decoders: mp1 mp1float ) DEA.L. mp2 MP2 (MPEG audio layer 2) (decoders: mp2 mp2float ) (encoders: mp2 libtwolame ) DEA.L. mp3 MP3 (MPEG audio layer 3) (decoders: mp3 mp3float ) (encoders: libmp3lame ) D.A.L. mp3adu ADU (Application Data Unit) MP3 (MPEG audio layer 3) (decoders: mp3adu mp3adufloat ) D.A.L. mp3on4 MP3onMP4 (decoders: mp3on4 mp3on4float ) D.A..S mp4als MPEG-4 Audio Lossless Coding (ALS) (decoders: als ) D.A.L. musepack7 Musepack SV7 (decoders: mpc7 ) D.A.L. musepack8 Musepack SV8 (decoders: mpc8 ) DEA.L. nellymoser Nellymoser Asao DEA.L. opus Opus (Opus Interactive Audio Codec) (decoders: libopus ) (encoders: libopus ) D.A.L. paf_audio Amazing Studio Packed Animation File Audio DEA.L. pcm_alaw PCM A-law / G.711 A-law D.A..S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media D.A..S pcm_dvd PCM signed 20|24-bit big-endian DEA..S pcm_f32be PCM 32-bit floating point big-endian DEA..S pcm_f32le PCM 32-bit floating point little-endian DEA..S pcm_f64be PCM 64-bit floating point big-endian DEA..S pcm_f64le PCM 64-bit floating point little-endian D.A..S pcm_lxf PCM signed 20-bit little-endian planar DEA.L. pcm_mulaw PCM mu-law / G.711 mu-law DEA..S pcm_s16be PCM signed 16-bit big-endian DEA..S pcm_s16be_planar PCM signed 16-bit big-endian planar DEA..S pcm_s16le PCM signed 16-bit little-endian DEA..S pcm_s16le_planar PCM signed 16-bit little-endian planar DEA..S pcm_s24be PCM signed 24-bit big-endian DEA..S pcm_s24daud PCM D-Cinema audio signed 24-bit DEA..S pcm_s24le PCM signed 24-bit little-endian DEA..S pcm_s24le_planar PCM signed 24-bit little-endian planar DEA..S pcm_s32be PCM signed 32-bit big-endian DEA..S pcm_s32le PCM signed 32-bit little-endian DEA..S pcm_s32le_planar PCM signed 32-bit little-endian planar DEA..S pcm_s8 PCM signed 8-bit DEA..S pcm_s8_planar PCM signed 8-bit planar DEA..S pcm_u16be PCM unsigned 16-bit big-endian DEA..S pcm_u16le PCM unsigned 16-bit little-endian DEA..S pcm_u24be PCM unsigned 24-bit big-endian DEA..S pcm_u24le PCM unsigned 24-bit little-endian DEA..S pcm_u32be PCM unsigned 32-bit big-endian DEA..S pcm_u32le PCM unsigned 32-bit little-endian DEA..S pcm_u8 PCM unsigned 8-bit D.A.L. pcm_zork PCM Zork D.A.L. qcelp QCELP / PureVoice D.A.L. qdm2 QDesign Music Codec 2 ..A.L. qdmc QDesign Music DEA.L. ra_144 RealAudio 1.0 (14.4K) (decoders: real_144 ) (encoders: real_144 ) D.A.L. ra_288 RealAudio 2.0 (28.8K) (decoders: real_288 ) D.A..S ralf RealAudio Lossless DEA.L. roq_dpcm DPCM id RoQ DEA..S s302m SMPTE 302M D.A..S shorten Shorten D.A.L. sipr RealAudio SIPR / ACELP.NET D.A.L. smackaudio Smacker audio (decoders: smackaud ) ..A.L. smv SMV (Selectable Mode Vocoder) D.A.L. sol_dpcm DPCM Sol DEA... sonic Sonic .EA... sonicls Sonic lossless DEA.L. speex Speex (decoders: libspeex ) (encoders: libspeex ) D.A..S tak TAK (Tom's lossless Audio Kompressor) D.A..S truehd TrueHD D.A.L. truespeech DSP Group TrueSpeech DEA..S tta TTA (True Audio) D.A.L. twinvq VQF TwinVQ D.A.L. vima LucasArts VIMA audio D.A.L. vmdaudio Sierra VMD audio DEA.L. vorbis Vorbis (decoders: vorbis libvorbis ) (encoders: vorbis libvorbis ) ..A.L. voxware Voxware RT29 Metasound D.A... wavesynth Wave synthesis pseudo-codec D.A.LS wavpack WavPack D.A.L. westwood_snd1 Westwood Audio (SND1) (decoders: ws_snd1 ) D.A..S wmalossless Windows Media Audio Lossless D.A.L. wmapro Windows Media Audio 9 Professional DEA.L. wmav1 Windows Media Audio 1 DEA.L. wmav2 Windows Media Audio 2 D.A.L. wmavoice Windows Media Audio Voice D.A.L. xan_dpcm DPCM Xan ..D... dvd_nav_packet DVD Nav packet ..D... klv SMPTE 336M Key-Length-Value (KLV) metadata DES... ass ASS (Advanced SSA) subtitle DES... dvb_subtitle DVB subtitles (decoders: dvbsub ) (encoders: dvbsub ) ..S... dvb_teletext DVB teletext DES... dvd_subtitle DVD subtitles (decoders: dvdsub ) (encoders: dvdsub ) ..S... eia_608 EIA-608 closed captions D.S... hdmv_pgs_subtitle HDMV Presentation Graphic Stream subtitles (decoders: pgssub ) D.S... jacosub JACOsub subtitle D.S... microdvd MicroDVD subtitle DES... mov_text MOV text D.S... mpl2 MPL2 subtitle D.S... pjs PJS (Phoenix Japanimation Society) subtitle D.S... realtext RealText subtitle D.S... sami SAMI subtitle DES... srt SubRip subtitle with embedded timing DES... ssa SSA (SubStation Alpha) subtitle DES... subrip SubRip subtitle D.S... subviewer SubViewer subtitle D.S... subviewer1 SubViewer v1 subtitle D.S... text raw UTF-8 text D.S... vplayer VPlayer subtitle D.S... webvtt WebVTT subtitle DES... xsub XSUB </pre> =='''all''' ffmpeg codecs that are supported== <pre> Codecs: D..... = Decoding supported .E.... = Encoding supported ..V... = Video codec ..A... = Audio codec ..S... = Subtitle codec ...S.. = Supports draw_horiz_band ....D. = Supports direct rendering method 1 .....T = Supports weird frame truncation ------ D V D 4xm 4X Movie D V D 8bps QuickTime 8BPS video D A 8svx_exp 8SVX exponential D A 8svx_fib 8SVX fibonacci D A 8svx_raw 8SVX rawaudio EV a64multi Multicolor charset for Commodore 64 EV a64multi5 Multicolor charset for Commodore 64, extended with 5th color (colram) DEA aac Advanced Audio Coding D A aac_latm AAC LATM (Advanced Audio Codec LATM syntax) D V D aasc Autodesk RLE DEA ac3 ATSC A/52A (AC-3) EA ac3_fixed ATSC A/52A (AC-3) D A adpcm_4xm ADPCM 4X Movie DEA adpcm_adx SEGA CRI ADX ADPCM D A adpcm_ct ADPCM Creative Technology D A adpcm_ea ADPCM Electronic Arts D A adpcm_ea_maxis_xa ADPCM Electronic Arts Maxis CDROM XA D A adpcm_ea_r1 ADPCM Electronic Arts R1 D A adpcm_ea_r2 ADPCM Electronic Arts R2 D A adpcm_ea_r3 ADPCM Electronic Arts R3 D A adpcm_ea_xas ADPCM Electronic Arts XAS D A adpcm_ima_amv ADPCM IMA AMV D A adpcm_ima_dk3 ADPCM IMA Duck DK3 D A adpcm_ima_dk4 ADPCM IMA Duck DK4 D A adpcm_ima_ea_eacs ADPCM IMA Electronic Arts EACS D A adpcm_ima_ea_sead ADPCM IMA Electronic Arts SEAD D A adpcm_ima_iss ADPCM IMA Funcom ISS DEA adpcm_ima_qt ADPCM IMA QuickTime D A adpcm_ima_smjpeg ADPCM IMA Loki SDL MJPEG DEA adpcm_ima_wav ADPCM IMA WAV D A adpcm_ima_ws ADPCM IMA Westwood DEA adpcm_ms ADPCM Microsoft D A adpcm_sbpro_2 ADPCM Sound Blaster Pro 2-bit D A adpcm_sbpro_3 ADPCM Sound Blaster Pro 2.6-bit D A adpcm_sbpro_4 ADPCM Sound Blaster Pro 4-bit DEA adpcm_swf ADPCM Shockwave Flash D A adpcm_thp ADPCM Nintendo Gamecube THP D A adpcm_xa ADPCM CDROM XA DEA adpcm_yamaha ADPCM Yamaha DEA alac ALAC (Apple Lossless Audio Codec) D A als MPEG-4 Audio Lossless Coding (ALS) D A amrnb Adaptive Multi-Rate NarrowBand D A amrwb Adaptive Multi-Rate WideBand D V amv AMV Video D V D anm Deluxe Paint Animation D V D ansi ASCII/ANSI art D A ape Monkey's Audio DES ass Advanced SubStation Alpha subtitle DEV D asv1 ASUS V1 DEV D asv2 ASUS V2 D A atrac1 Atrac 1 (Adaptive TRansform Acoustic Coding) D A atrac3 Atrac 3 (Adaptive TRansform Acoustic Coding 3) D V D aura Auravision AURA D V D aura2 Auravision Aura 2 D V D avs AVS (Audio Video Standard) video D V D bethsoftvid Bethesda VID video D V D bfi Brute Force & Ignorance D A binkaudio_dct Bink Audio (DCT) D A binkaudio_rdft Bink Audio (RDFT) D V binkvideo Bink video DEV D bmp BMP image D V D c93 Interplay C93 D V D camstudio CamStudio D V D camtasia TechSmith Screen Capture Codec D V D cavs Chinese AVS video (AVS1-P2, JiZhun profile) D V D cdgraphics CD Graphics video D V D cinepak Cinepak D V D cljr Cirrus Logic AccuPak D A cook COOK D V D cyuv Creative YUV (CYUV) DEA dca D V D dfa Chronomaster DFA DEV D dnxhd VC3/DNxHD DEV dpx DPX image D A dsicinaudio Delphine Software International CIN audio D V D dsicinvideo Delphine Software International CIN video DES dvbsub DVB subtitles DES dvdsub DVD subtitles DEV D dvvideo DV (Digital Video) D V D dxa Feeble Files/ScummVM DXA DEA eac3 ATSC A/52 E-AC-3 D V D eacmv Electronic Arts CMV video D V D eamad Electronic Arts Madcow Video D V D eatgq Electronic Arts TGQ video D V eatgv Electronic Arts TGV video D V D eatqi Electronic Arts TQI Video D V D escape124 Escape 124 DEV D ffv1 FFmpeg video codec #1 DEVSD ffvhuff Huffyuv FFmpeg variant DEA flac FLAC (Free Lossless Audio Codec) DEV D flashsv Flash Screen Video EV flashsv2 Flash Screen Video Version 2 D V D flic Autodesk Animator Flic video DEVSD flv Flash Video (FLV) / Sorenson Spark / Sorenson H.263 D V D fraps Fraps D V D frwu Forward Uncompressed DEA g722 G.722 ADPCM DEA g726 G.726 ADPCM DEV D gif GIF (Graphics Interchange Format) D A gsm GSM D A gsm_ms GSM Microsoft variant DEV D h261 H.261 DEVSDT h263 H.263 / H.263-1996 D VSD h263i Intel H.263 EV h263p H.263+ / H.263-1998 / H.263 version 2 D V D h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 D V D h264_vdpau H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (VDPAU acceleration) DEVSD huffyuv Huffyuv / HuffYUV D V D idcinvideo id Quake II CIN video D V D iff_byterun1 IFF ByteRun1 D V D iff_ilbm IFF ILBM D A imc IMC (Intel Music Coder) D V D indeo2 Intel Indeo 2 D V D indeo3 Intel Indeo 3 D V indeo5 Intel Indeo Video Interactive 5 D A interplay_dpcm DPCM Interplay D V D interplayvideo Interplay MVE video D V j2k DEV D jpegls JPEG-LS D V D jv Bitmap Brothers JV video D V kgv1 Kega Game Video D V D kmvc Karl Morton's video codec D V D lagarith Lagarith lossless EV libdirac libdirac Dirac 2.2 DEA libgsm libgsm GSM DEA libgsm_ms libgsm GSM Microsoft variant EA libmp3lame libmp3lame MP3 (MPEG audio layer 3) DEA libopencore_amrnb OpenCORE Adaptive Multi-Rate (AMR) Narrow-Band D A libopencore_amrwb OpenCORE Adaptive Multi-Rate (AMR) Wide-Band DEV libschroedinger libschroedinger Dirac 2.2 DEA libspeex libspeex Speex Encoder EV libtheora libtheora Theora EA libvorbis libvorbis Vorbis DEV libvpx libvpx VP8 EV libx264 libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 EV libxvid libxvidcore MPEG-4 part 2 EV ljpeg Lossless JPEG D V D loco LOCO D A mace3 MACE (Macintosh Audio Compression/Expansion) 3:1 D A mace6 MACE (Macintosh Audio Compression/Expansion) 6:1 D V D mdec Sony PlayStation MDEC (Motion DECoder) D V D mimic Mimic DEV D mjpeg MJPEG (Motion JPEG) D V D mjpegb Apple MJPEG-B D A mlp MLP (Meridian Lossless Packing) D V D mmvideo American Laser Games MM Video D V D motionpixels Motion Pixels video D A mp1 MP1 (MPEG audio layer 1) D A mp1float MP1 (MPEG audio layer 1) DEA mp2 MP2 (MPEG audio layer 2) D A mp2float MP2 (MPEG audio layer 2) D A mp3 MP3 (MPEG audio layer 3) D A mp3adu ADU (Application Data Unit) MP3 (MPEG audio layer 3) D A mp3adufloat ADU (Application Data Unit) MP3 (MPEG audio layer 3) D A mp3float MP3 (MPEG audio layer 3) D A mp3on4 MP3onMP4 D A mp3on4float MP3onMP4 D A mpc7 Musepack SV7 D A mpc8 Musepack SV8 DEVSDT mpeg1video MPEG-1 video D V DT mpeg1video_vdpau MPEG-1 video (VDPAU acceleration) DEVSDT mpeg2video MPEG-2 video DEVSDT mpeg4 MPEG-4 part 2 D V DT mpeg4_vdpau MPEG-4 part 2 (VDPAU) D VSDT mpegvideo MPEG-1 video D V DT mpegvideo_vdpau MPEG-1/2 video (VDPAU acceleration) D VSDT mpegvideo_xvmc MPEG-1/2 video XvMC (X-Video Motion Compensation) DEVSD msmpeg4 MPEG-4 part 2 Microsoft variant version 3 D VSD msmpeg4v1 MPEG-4 part 2 Microsoft variant version 1 DEVSD msmpeg4v2 MPEG-4 part 2 Microsoft variant version 2 D V D msrle Microsoft RLE DEV D msvideo1 Microsoft Video-1 D V D mszh LCL (LossLess Codec Library) MSZH D V D mxpeg Mobotix MxPEG video DEA nellymoser Nellymoser Asao D V D nuv NuppelVideo/RTJPEG DEV D pam PAM (Portable AnyMap) image DEV D pbm PBM (Portable BitMap) image DEA pcm_alaw PCM A-law D A pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media D A pcm_dvd PCM signed 20|24-bit big-endian DEA pcm_f32be PCM 32-bit floating point big-endian DEA pcm_f32le PCM 32-bit floating point little-endian DEA pcm_f64be PCM 64-bit floating point big-endian DEA pcm_f64le PCM 64-bit floating point little-endian D A pcm_lxf PCM signed 20-bit little-endian planar DEA pcm_mulaw PCM mu-law DEA pcm_s16be PCM signed 16-bit big-endian DEA pcm_s16le PCM signed 16-bit little-endian D A pcm_s16le_planar PCM 16-bit little-endian planar DEA pcm_s24be PCM signed 24-bit big-endian DEA pcm_s24daud PCM D-Cinema audio signed 24-bit DEA pcm_s24le PCM signed 24-bit little-endian DEA pcm_s32be PCM signed 32-bit big-endian DEA pcm_s32le PCM signed 32-bit little-endian DEA pcm_s8 PCM signed 8-bit DEA pcm_u16be PCM unsigned 16-bit big-endian DEA pcm_u16le PCM unsigned 16-bit little-endian DEA pcm_u24be PCM unsigned 24-bit big-endian DEA pcm_u24le PCM unsigned 24-bit little-endian DEA pcm_u32be PCM unsigned 32-bit big-endian DEA pcm_u32le PCM unsigned 32-bit little-endian DEA pcm_u8 PCM unsigned 8-bit DEA pcm_zork PCM Zork DEV D pcx PC Paintbrush PCX image DEV D pgm PGM (Portable GrayMap) image DEV D pgmyuv PGMYUV (Portable GrayMap YUV) image D S pgssub HDMV Presentation Graphic Stream subtitles D V D pictor Pictor/PC Paint DEV D png PNG image DEV D ppm PPM (Portable PixelMap) image D V D ptx V.Flash PTX image D A qcelp QCELP / PureVoice D A qdm2 QDesign Music Codec 2 D V D qdraw Apple QuickDraw D V D qpeg Q-team QPEG DEV D qtrle QuickTime Animation (RLE) video D V D r10k AJA Kona 10-bit RGB Codec D V D r210 Uncompressed RGB 10-bit DEV rawvideo raw video DEA real_144 RealAudio 1.0 (14.4K) encoder D A real_288 RealAudio 2.0 (28.8K) D V D rl2 RL2 video DEA roq_dpcm id RoQ DPCM DEV D roqvideo id RoQ video D V D rpza QuickTime video (RPZA) DEV D rv10 RealVideo 1.0 DEV D rv20 RealVideo 2.0 D V D rv30 RealVideo 3.0 D V D rv40 RealVideo 4.0 D A s302m SMPTE 302M DEV sgi SGI image D A shorten Shorten D A sipr RealAudio SIPR / ACELP.NET D A smackaud Smacker audio D V D smackvid Smacker video D V D smc QuickTime Graphics (SMC) DEV D snow Snow D A sol_dpcm DPCM Sol DEA sonic Sonic EA sonicls Sonic lossless D V D sp5x Sunplus JPEG (SP5X) DES srt SubRip subtitle D V D sunrast Sun Rasterfile image DEV D svq1 Sorenson Vector Quantizer 1 / Sorenson Video 1 / SVQ1 D VSD svq3 Sorenson Vector Quantizer 3 / Sorenson Video 3 / SVQ3 DEV D targa Truevision Targa image D VSD theora Theora D V D thp Nintendo Gamecube THP video D V D tiertexseqvideo Tiertex Limited SEQ video DEV D tiff TIFF image D V D tmv 8088flex TMV D A truehd TrueHD D V D truemotion1 Duck TrueMotion 1.0 D V D truemotion2 Duck TrueMotion 2.0 D A truespeech DSP Group TrueSpeech D A tta True Audio (TTA) D A twinvq VQF TwinVQ D V D txd Renderware TXD (TeXture Dictionary) image D V D ultimotion IBM UltiMotion DEV D v210 Uncompressed 4:2:2 10-bit D V D v210x Uncompressed 4:2:2 10-bit D V vb Beam Software VB D V D vc1 SMPTE VC-1 D V D vc1_vdpau SMPTE VC-1 VDPAU D V D vcr1 ATI VCR1 D A vmdaudio Sierra VMD audio D V D vmdvideo Sierra VMD video D V D vmnc VMware Screen Codec / VMware Video DEA vorbis Vorbis D VSD vp3 On2 VP3 D V D vp5 On2 VP5 D V D vp6 On2 VP6 D V D vp6a On2 VP6 (Flash version, with alpha channel) D V D vp6f On2 VP6 (Flash version) D V D vp8 On2 VP8 D V D vqavideo Westwood Studios VQA (Vector Quantized Animation) video D A wavpack WavPack D A wmapro Windows Media Audio 9 Professional DEA wmav1 Windows Media Audio 1 DEA wmav2 Windows Media Audio 2 D A wmavoice Windows Media Audio Voice DEVSD wmv1 Windows Media Video 7 DEVSD wmv2 Windows Media Video 8 D V D wmv3 Windows Media Video 9 D V D wmv3_vdpau Windows Media Video 9 VDPAU D V D wnv1 Winnov WNV1 D A ws_snd1 Westwood Audio (SND1) D A xan_dpcm DPCM Xan D V D xan_wc3 Wing Commander III / Xan D V D xan_wc4 Wing Commander IV / Xxan D V D xl Miro VideoXL DES xsub DivX subtitles (XSUB) D V yop Psygnosis YOP Video DEV D zlib LCL (LossLess Codec Library) ZLIB DEV D zmbv Zip Motion Blocks Video Note, the names of encoders and decoders do not always match, so there are several cases where the above table shows encoder only or decoder only entries even though both encoding and decoding are supported. For example, the h263 decoder corresponds to the h263 and h263p encoders, for file formats it is even worse. </pre> =Download videos from YT channel= # youtube-dl -f best -ciw -o "%(title)s.%(ext)s" -v https://www.youtube.com/channel/UCUAVzSGkkTa-IoMx_x1XK4Q =Cool effects using ffplay= $ ffplay -i /dev/video0 -vf 'lagfun=decay=0.98[tmp]; [tmp] hue=180*sin(t)' =Using ffmpeg with hardware acceleration= $ ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i bulkerasenew.mp4 -c:v h264_vaapi -b:v 2M -maxrate 2M output.mp4 3ea2b4b7c219c45bf97e3134c2f660d44bd2a575 0 613 2850 2849 2025-08-14T07:58:25Z Pvdm 2 /* Edit in one metadatafile */ wikitext text/x-wiki View PDF metadata: # exiftool file.pdf View specific metadata: # exiftool -Creator file.pdf # find . -type f -iname '*.pdf' -exec exiftool -Creator {} \; Set metadata: # exiftool -Creator='barbapappa' file.pdf # find . -type f -iname '*.pdf' -exec exiftool -Creator='barbapappa' {} \; to preserve date/time: -P to delete backup file that is created: -delete_original[!] # find . -type f -iname '*.pdf' -exec exiftool -P -overwrite_original -Producer='www.bladiebla.nl' -Creator='barbapappa' {} \; # find . -type f -iname '*.pdf' -exec exiftool -P -delete_original! {} \; =Edit in one metadatafile= Make a parameter file <pre> -Title=Mijn Titel -Author=Mijn Naam -Creator=Microsoft Word -Producer=Adobe PDF Library 15.0 -Subject=Korte samenvatting -Keywords=tag1, tag2, tag3 -CreateDate=2025:08:14 08:00:00 -ModifyDate=2025:08:14 08:00:00 </pre> and apply with: # exiftool -@ meta.args -overwrite_original pdfbestand.pdf =workflow= <pre> #!/bin/bash set -e echo alle odg naar pdf zetten libreoffice --headless --convert-to pdf *.odg echo alle pdf files in 1 groot document pdfunite {1..22}.pdf samengevoegd.pdf echo pdftk om fouten weg te krijgen pdftk samengevoegd.pdf output rc1.pdf echo de metadata erin exiftool -@ metadata.csv rc1.pdf echo haal oude metadata weg en houd alleen de laatste huidige qpdf --linearize rc1.pdf rc2.pdf echo echo De file rc.2 is de output echo </pre> 4f7dec8822a35b268690302bfa10e87da34fc9bf